Multi-Level Cascading Fields in JSM Without Using Forms

[Harald Heinz]

Hi, for our customer port request type, I need to implement a cascading field setup where:

• Field A determines the options in Field B
• and Field B then determines the options in Field C

What’s the best way to implement this without using Forms?
If using Forms is unavoidable, are the fields used within Forms later available for filtering or reporting?

[John Funk · Accepted solution]

Hi Harald,

No, that is not native in JSM. You would either need to use the Advanced Form or use the ScriptRunner Behaviours app. And yes, you can use the Form fields in Automation Rules, but not in JQL (that I am aware of). 

[Ugnius Aušra · Accepted solution]

Hello @Harald Heinz 

From my experience, you can't make anywhere in Jira without using forms.

If using Forms is unavoidable, are the fields used within Forms later available for filtering or reporting? You can create custom fields and link it to field created in form. 

[Harald Heinz]

Ok, so I understand when I have to use forms

• Linked custom fields would work to be 
  • multi-level cascading
  • fields would be filterable
    
    
• But would non-linked field entries be filterable in any way?

[Ugnius Aušra]

• But would non-linked field entries be filterable in any way?

Form fields are more just for FE side (Front end) as i like to say. By what i mean is, you or customer through customer portal can enter data in form fields, but you can't make any reports, or filter by them if they are not linked to Jira field (Systemic or custom).

[Trudy Claspill]

Hello @Harald Heinz 

If you use Forms to create "multi-level cascading select" fields using the logic of Forms, and connect those to Single Select custom fields in the underlying work item, the Single Select custom fields will not act as multi-level cascading fields without additional functionality. 

Jira supports a maximum of only 2 levels in a cascading select list custom field. If you need more than 2 levels then you need a third party product.

Scriptrunner Behaviours is one such product where you would have to create code to manage the filtering of a lower level field based on a higher level field in the cascade. I have worked on that exact implementation and it can become very complicated. It is also requires extensive and complex code to manage, for instance, resetting lower level fields if a high level field is changed when editing an item.

A more complete solution is the Multi-Level Cascading app from Sourcesense. You can find that and other apps from the Atlassian Marketplace. This search will help you find some apps that might satisfy your requirement.

https://marketplace.atlassian.com/search?query=multi%20level%20cascading%20select