Since the data structure format changed. Please refer to the Data Structure (Automation) section for further details.
On this page
Field Configuration
Before starting the field configuration, please follow the instructions for creating custom fields: Create a Custom Field
Step 1: Set a name and description
Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.
Step 2: Add options
This field allows you to create as many levels as needed to cover your requirements. You can also define display options or if all levels have to be selected to prevent empty fields.
Step 3 (Optional): Add custom option labels
In conjunction with the select options, you can further enhance customization by adding custom labels for each option level. To do so, enable the "enable field label per parent" option and click "Edit field level" for the specific option level you wish to customize.
Step 4 (Optional): Single or multi select
If enabled users can select multiple values per level. Child options will be merged for the next level. This will also change the way the values are displayed in the issue.
Step 5 (Optional): Customize display and required status
Regarding the display option, you have the flexibility to choose between showcasing the entire path or just the final option. For example a full path may look like this: Option 1 -> Option 1.1 -> Option 1.1.1 , whereas last step like this: Option 1.1.1.
If you want the cascading select to be completely selected, check the required selection toggle. This important if you want the field to be required.
If you select “Required Selection”, any sub-levels will be automatically chosen if only one child option is available.
Step 6 (Optional): Restrict visibility
By restricting the visibility of the options, only selected users can view the potential values in the issue view. Please note that they can still see the selected value, but are unable to change it.
You can choose to restrict visibility by roles, individual users, or groups.
Enabling this setting will switch the saving location to 'storage,' making it incompatible with JSM.
If a user is not permitted to see the options, the edit screen will appear as shown. Please be aware that the selected value will still be visible.
Please note that administrators are always able to see the options.
A note to additional storage
In the case of extensive configurations with a multitude of options or levels (exceeding 500), you might encounter the maximum storage capacity for the field configuration. In such instances, a warning will prompt you to consider upgrading to a larger storage capacity to accommodate additional options.
Please be aware that modifying this storage option will result in the complete deactivation of the cascading select functionality in Jira Service Management, impacting both the request form and portal view. This is due to technical limitations.
Field view and edit
Related Use Cases
More use cases are coming soon. In the meantime, check out our other use cases.
Jira Service Management (JSM)
Before you can add a custom field for Jira Service Management (JSM) projects, you first need to setup the custom field: https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/12288051/Cascading+Select#Field-Configuration. Then follow the guide to use the field in the request form or the portal view: Add Custom Fields to Jira Service Management
JQL expression
Basic example
You can search for option name of parts it.
Say you have a selection like this: Frontend → Main Menu → Typo
Then you can search for any options like this
"Cascading Select" ~ "Main Menu" "Cascading Select" ~ "Typo"
Search for several options
You can also search for several options, which can be separated by comma for better readability
"Cascading Select" ~ "Frontend, Main Menu, Typo"
Search for specific path
You can also search for an exact path, in case you have options with the same name.
Therefore copy the value in the issue view
"Single Select" ~ "Frontend → Main Menu → Typo"
"Multi Select" ~ "Backend
↳ Error Message
↳ Typo"
Data Structure (Automation)
Since the data structure format changed. Items below selection are now also Arrays to be capable of storing multi select values. This change might break existing automation rules!
To set the value via automation, you need the following object structure
{
"selection": [
[
{
"id": number,
"name": string,
"children": number[]
}
]
]
}
We know that this is kind of complex (depending on the number of levels). So here’s an example of the configuration used in the screenshots above.
{
"selection": [
[{
"id": "0",
"name": "Option 1",
"children": [
"2" <-- the id of Option 1.1
]
},
{
"id": "1",
"name": "Option 2"
}],
[{
"id": "2",
"name": "Option 1.1",
"children": [
"3" <-- the id of Option 1.1.1
]
}],
[{
"id": "3",
"name": "Option 1.1.1",
}]
]
}
Tip: To get the actual values, we recommend to print out the desired value first. this can be done via an automation rule that writes the value into a simple text field.