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?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

Ugnius Aušra

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.

John Funk

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).

Trudy P 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

All comments

Ugnius Aušra

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).

John Funk

Hi Harald,

Trudy P Claspill

Hello @Harald Heinz

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.

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

Kavitha Vaikunthavasan _Seibert-Products_

Hi @Harald Heinz this is exactly what Awesome Custom Fields (ACF) is built for, and you don't need Forms to make it work.

ACF's Cascading Select field supports many levels, so your A → B → C setup (and beyond) is fully supported out of the box.

Crucially for your use case: ACF's Cascading Select works directly in the JSM Customer Portal, no Forms required. Your customers will see the dependent fields update dynamically as they make selections.

Step-by-step setup instructions here: ACF Cascading Select Documentation

You can try it free on the Atlassian Marketplace: Awesome Custom Fields

Let us know if you have any questions! 😊

Best

Kavitha

Wajdi from VIP.LEAN Solutions

Hi @Harald Heinz

This article describes exactly your use case, based on the Jira system and standard custom fields, which you can apply to your existing portal screen:

Bringing Dynamic Field Behaviours to the JSM Customer Portal

Best regards, Wajdi

Evie Z.

@Wajdi from VIP_LEAN Solutions

This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .

Thank you for your understanding!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management