Multi Level Cascade Field - v3.1.0
Release Notes: Multi Level Cascade Field - v3.1.0
Release Date: June 16th, 2025
The purpose of this document is to provide a comprehensive overview of the Multi Level Cascade Field feature. It explains how the feature works, outlines its configuration options, and describes use cases where it can be effectively applied. This guide is intended for end users, administrators, and developers who need to understand or implement cascading selection fields with multiple hierarchical levels in their workflows or forms. The document ensures that users can leverage the feature to create dynamic, context-driven field selections that enhance data accuracy and user experience.
- 1 Overview
- 2 Use Case: Select City for Stock Delivery based on Region/Country
- 3 Key Features
- 4 Instructions for Use
- 4.1 Add Multi Level Cascade Field in Table Grid Next Generation app
- 4.2 Add Multi Level Cascade Field in Custom Fields screen
- 4.3 Configure Levels with Jira Fields Data Source
- 4.4 Configure Levels with JQL Data Source
- 4.5 Configure Levels with SQL Data Source
- 4.6 Configure Levels with REST Data Source
- 4.7 Set Default Value for Multi Level Cascade Field
- 4.8 Edit and Delete Multi Level Cascade Fields
- 4.9 Apply Multi Level Cascade Field to Issue Screen
- 4.10 Edit Multi Level Cascade Field on Issue Screen
- 5 Feedback and Support
- 6 Conclusion
Overview
Idea:
Multi Level Cascade Field is designed to enable hierarchical field selections, where each choice dynamically filters the options available in the next level. This structure allows users to make selections through multiple, logically dependent dropdowns. For example, choosing a Region, then a Country, and finally a City. Each level narrows down the available options based on the selection made in the previous level, helping to streamline data entry and reduce human error.
Goal:
The goal of the Multi Level Cascade Field is to enhance user experience and data accuracy by guiding users through a step-by-step selection process that reflects real-world hierarchies. By implementing this field type, teams can standardize data input, ensure contextual relevance, and simplify complex decision trees. Particularly useful in issue categorization, service request forms, or reporting parameters.
Use Case: Select City for Stock Delivery based on Region/Country
A user needs to select a City for stock delivery. Instead of showing all cities, the system uses a Multi Level Cascade:
User selects a Region (e.g., Europe)
Then selects a Country within that region (e.g., France)
Finally selects a City (e.g., Paris)
This ensures accurate location selection and avoids irrelevant options.
Key Features
Configure Multi Level Cascade Field
Users can configure multi level cascade fields as custom fields to show logically dependent dropdowns.
Delete Multi Level Cascade Field
Users can delete the existing multi level cascade field configuration clicking “Delete” button on each one.
Set Default Value for Multi Level Cascade Field
Users can set default value for configured levels in multi level cascade fields.
Apply Multi Level Cascade Field to Issue Screen
Users can select value for multi level cascade field on Issue Screen.
Instructions for Use
Add Multi Level Cascade Field in Table Grid Next Generation app
Open Manage apps page in Jira Administration
Click Multi Level Cascade Configuration
Click Add Field button
Fill in Name and Description of your field
Configure levels
Click Save button to save field
Add Multi Level Cascade Field in Custom Fields screen
Open Work items page in Jira Administration
Click Custom fields in Fields section
Click Create custom field button
Select Multi Level Cascade Field and click Next
Fill in Name and Description of your field
Click Create
Select Issue Types and Projects to configure which issues that your field will appear
Click Create
Check screens that you want to display your field and click Update
Configure Levels with Jira Fields Data Source
On Multi Level Cascade Configuration screen, select “Jira Fields” as data source
Click
to add level
Fill in Label (to display as name of dropdown) and Identifier (to identify the value of the dropdown and be used in placeholder) for each level
Select a Jira field in Field to get data
Select an attribute of the selected Jira field in Display column field to show value in the dropdown list
Click
to save level
Configure Levels with JQL Data Source
On Multi Level Cascade Configuration screen, select “JQL” as data source
Click
to add level
Fill in Label (to display as name of dropdown) and Identifier (to identify the value of the dropdown and be used in placeholder) for each level
Enter JQL query to define the scope of Jira issues
You can use value placeholder to replace actual values of levels at runtime
Format: {level:identifier:attribute}
Example: {level:issuetype:id}
represents the value of the id
attribute for the level identified by issuetype
.
Click Validate to check the validation of JQL query
Select a Jira field in Display column field to show value in the dropdown list
If JQL query contains placeholder, you have to type the column name in Display column field
Click
to save level
Configure Levels with SQL Data Source
On Multi Level Cascade Configuration screen, select a data source with SQL type
Click
to add level
Fill in Label (to display as name of dropdown) and Identifier (to identify the value of the dropdown and be used in placeholder) for each level
Enter SQL query and click Get data to query data
You can use value placeholder to replace actual values of levels at runtime
Format: {level:identifier:attribute}
Example: {level:issuetype:id}
represents the value of the id
attribute for the level identified by issuetype
.
Select a column in Display column field to select which column data appear in the dropdown list
If SQL query contains placeholder, you have to type the column name in Display column field
Click
to save level
Configure Levels with REST Data Source
On Multi Level Cascade Configuration screen, select a data source with REST type
Click
to add level
Fill in Label (to display as name of dropdown) and Identifier (to identify the value of the dropdown and be used in placeholder) for each level
Enter JSON Path query or Relative URL to query data
You can use value placeholder to replace actual values of levels at runtime
Format: {level:identifier:attribute}
Example: {level:issuetype:id}
represents the value of the id
attribute for the level identified by issuetype
.
Click Get data
Select a column in Display column field to select which column data appear in the dropdown list
If SQL query contains placeholder, you have to type the column name in Display column field
Click
to save level
Set Default Value for Multi Level Cascade Field
Open a configured Multi Level Cascade Field
Click Default Values tab
Select default values for levels that were configured in Levels tab
Click Save to save the level configuration
Edit and Delete Multi Level Cascade Fields
Open Apps page in Jira Administration
Click Multi Level Cascade Configuration
Click
to edit field and click
to delete field
Apply Multi Level Cascade Field to Issue Screen
Multi Level Cascade Field can’t be displayed on Customer Portal screen in Jira Service Management project.
Create issue in Projects and Issue Types that have been configured to display your Multi Level Cascade Field
Select values for your multi level cascade field, then click Save
Click Create to create issue with your field
Edit Multi Level Cascade Field on Issue Screen
Open issue that has been configured to display your Multi Level Cascade Field
Click on your field to edit its value
Select values for your multi level cascade field
Click Save to save your field
Feedback and Support
For more information, visit our Support Portal here.
Conclusion
Multi Level Cascade feature enhances user interaction by providing a structured, hierarchical selection process that ensures data relevance and accuracy. By dynamically filtering options based on previous selections, it simplifies complex workflows and reduces input errors. Whether used for categorizing issues, filtering reports, or segmenting data, this feature offers a more intuitive and efficient user experience.
We encourage you to explore its capabilities and integrate it into your workflows to streamline operations and improve data consistency.