MLCS Documentation
MLCS Documentation

Multi Level Cascading Select (MLCS) is a add-on for the Atlassian Jira that models a new custom field. The new custom field allows you to have a cascading select with a multi level selection.

 

USER GUIDE

Issue creation and edit
Creating and editing an issue with a Multi level Cascade custom field value is really a simple task. During the creation of an issue is possible to select from a multi cascade list the options for the current value.

noreel

Editing a value is possible through the InLine edit feature or through the normal issue editing interface. To carry out the In line editing, simply point the mouse on the Multi Level Cascade Select value in the issue view screen and click for editing:

noreel

noreel

 

Searcher

To use a Multi Level Cascade value to search issues, in the Issue Navigator add your MLCS custom field to the input filter for the search. A multi select cascade list will be loaded with the list of configured values:

noreel

Select the desired value and trigger the search.

noreel

1) if you select “Any” for the first level, “Any” will apply to all the levels and the search will return all the issues that have any value for our custom field. Issues with no custom field value will be excluded from the results.
2) if you select “none” for the first level,”none” will apply to all the levels and the search will return all the issues with no value selected for this field. Any issue having any not null value for the custom field will be excluded from the search results.
3) if you select a list of options that ends with a “none” value, the search results will include only the issues with the exact value of the custom field that corresponds to the list of options in input.
Example : I1= 1.1.1, I2=1.1.1.1, I3=1.1.1.2
Search : 1.1.1
Results : I1

4) if you select a list of options that ends with a “Any” value,the search results will include all the issues with the exact value and all the issues that contain children of that value.
Example : I1= 1.1.1, I2=1.1.1.1, I3=1.1.1.2
Search : 1.1.1
Results : I1-I2-I3

 

Advanced Search

If you directly write your JQL queries, MLCS fields can be searched using the IN operator or a JQL function defined by the add-on, “MultiLevelCascadeOption()”.

IN operator

The IN operator produces a result set which is wider than the one we get using the “MultiLevelCascadeOption()” JQL function: it will hit all the cases where the given sequence of option values appears among the selected ones. This is better explained by example:

suppose we have a MLCS custom field “Place” with option structure like

Europe
> Italy
> France
America
> Mexico
> USA

then the JQL query

Place in (America,USA)

will retrieve all the issues such that “Place” evaluates to anything that contains “America” followed by “USA”, regardless of the depth of the options: this means that, if we add “America” as a child option of “Italy”, and “USA” as a child option of the second “America”, so that the option structure is made into

Europe
> Italy
> America
> USA
> France
America
> Mexico
> USA
then the issues such that “Place” evaluates to “Europe – Italy – America – USA” will be retrieved (while “MultiLevelCascadeOption(America,USA)” would retrieve only the issues in which “America” is the root option, followed by “USA”)

The IN operator alse supports the “None” keyword, so

Place in (Europe,None)

will retrieve all the issues such that an option of value “Europe” is selected while no deeper option is.

The IN operator can be used also with option IDs, but the None keyword won’t work in that case (it will be ignored).

IS operator

The IS operator is only used to find out which issues have the MLCS custom field set to any value, so in our example the two possible queries using IS are:

Place is EMPTY

which will retrieve all the issues such that “Place” is not set at all;

Place is not EMPTY

which retrieves all issues such that “Place” is set to any value.

JQL function (DEPRECATED)

The function MultiLevelCascadeOption() gets one or more comma-separated parameters, that can be option IDs and/or values

This function is deprecated in favor of the IN operator and will be removed in future releases

Examples:

NOTE: even though option values are not JIRA-wise unique, two silbling options cannot get the same value, so the result of someField in MultilevelCascadeOption("something", "somethingElse", "somethingFurther") is actually unambiguously defined. There is, though, a rare case of ambiguity: it happens if there exists an MLCS field having two options such that one option’s value equals the ID of the other option. In most cases, option hierarchy will establish a unique interpretation for queries, but sometimes a query will actually be ambiguous: in thor really rare cases, a warning dialog will be displayed:

If you programmaticaly call the function, consider using IDs instead of values if you have to deal with option values which are numbers (IDs are always JIRA-wise unique).

 

Reports

A MLCS field can be used in gadgets and reports, like the filter statistics or the pie chart gadgets:

Reports1
Reports2

 

SUPPORT SITE

We support Multi-Level Cascading Select. You can visit the support site to get help.

 

INSTALLATION GUIDE

MLCS can be installed either from the Marketplace or as a jar.

Log in into Jira as an administrator and go to Administration > Plugins > Find new Add-ons.
Write “Multi Level Cascading Select List” in the search box and then click on “Buy now” or “Free trial”.

If your Jira instance cannot access to the Marketplace, you can the download of the package here, and upload it through the Atlassian Universal Plugin Manager in the Jira Administration section: Administration > Plugins > Manage Add-ons > Upload plugin.

Note
If you are upgrading from versions < 3.0, you need to rebuild the JIRA index.

 

 

ADMINISTRATION GUIDE

To create a new Multi Level Cascading Select List field, go to Administration > Issues > Custom Fields > Add Custom Field:

noreel

and select the Multi-Level Cascading Select field type. Add name, description, context and then select in which screens you want to add the field.

To add values to the field, select Configure from the field list:

noreel

 

and then Configure Options.

After you’ve added the values for the first level, To add new options as children of an existing one, click the Configure link and start adding new options:

noreel

noreel

It is possible to configure multiple levels:

noreel

 

You can select a default value for the field, clicking on the link Configure Default Value:

noreel

 

Contatta il nostro Team! Contattaci senza impegno per richiedere maggiori informazioni sui prodotti e servizi, ti ricontatteremo nel più breve tempo possibile.
 I dati che ci fornirai saranno trattati nel rispetto della tua privacy, e non verranno per alcun motivo ceduti a terzi.
Messaggio inviato correttamente.