...
There are two ways to refer to MLCS fields in a JQL query:
By field name:
Use the name of the of a MLCS field to refer to that specific custom field. For this search, a JSON-like value is required.
...
| Info |
|---|
To assist you in writing the JSON-like value, enter the name of the MLCS field along with a valid operator to retrieve all unique selection sets from your issues for that specific field.  |
By issue property:
issue.property[“com.sourcesense.mlcs”].lv0lv(n) and it’s alias, mlcs_lv0lv(n). They both work similarly, but . The latter is an alias that we created an alias to make it easier to write the property. Change the number of lv (n) with the lv number to match the level of the option you are looking for.
| Info |
|---|
|
In the following section, we will see how we can exploit the MLCS integration in JQL queries to search for issues, even without admin privileges (therefore with no access to the MLCS field configuration).
Find options level by MLCS field name
If we do not have admin access to the custom field page and we do not know the configuration tree, we can use the suggestions from the autocomplete mask activated by typing the operator after the name of the field. This will retrieve all the occurrences of that field and the relative selections.
...
Once the suggestion is chosen, a JSON-like value populates the JQL query, indicating the filter applied. Now, we have access to the option names (label) and the relative IDs (value).
Search for issues where the option appears in any MLCS field.
You can specify the name (label) of an option and the level where it’s supposed to be, to filter issues on any MLCS field that contains that selection. This is the syntax: mlcs_lv(n) = <option label>.
Use case scenario
Given this sample configuration:
...
The goal is to select the issues that contain the option “1.1”. Multiple MLCS custom fields share this same option, and we need to retrieve all of them.
...