🎉 New! Cascading Fields in JSM Forms

[#1]

Hello Atlassian community 👋

We’re thrilled to announce an exciting new feature in Jira Service Management: the ability to build cascading fields in Forms! 

Cascading fields allow you to create a dynamic hierarchy of options where a selection in one field determines the available options in another. This is particularly useful for those of you with complex service request workflows, as it ensures that your help seekers can provide the most accurate and relevant information when submitting requests.

On top of that, you can now link your cascading fields in Forms directly to a Jira cascading field.

How it works

To start using cascading fields, navigate to the form builder within your service project. Here, you’ll find the option to add cascading fields to your forms. Once added, you can define the options for each level and establish the parent-child relationships between them.

To link a cascading field in a form to a Jira cascading field, select the link option in the field settings. You’ll then be able to choose from existing Jira cascading fields within your project.

This feature is now available to everyone, and we’re excited to see how you’ll use it to enhance your service management processes. Whether you’re streamlining IT requests, managing complex HR workflows, or anything in between, cascading fields will provide the flexibility and detail you need.

What's next?

Thank you to everyone who suggested this addition! Please let us know how you go with the new feature in the comments below.

Thank you for being a part of our community and for your continued support as we work to make JSM the best tool it can be.

Happy cascading! 

[Elena Lurye]

That's a great news! I started using it already last week.

[Sandra Fuchs]

I see there are validations (Required response) enabled, but is there a way to have the validation applicable to the child? 

[Iman Attia]

It would be great if you could select multiple parents with the same child choices too! 

[Ojelola Ojelabi- Rallybetter_com]

This is great! @Sam Knight 

[Evan Fishman - Rallybetter_com]

👍🏻

[Urmo]

Hi, 

Will it work with assets? 

[Rick David]

Hi, does anyone knows if this can be used to link the 'Assignment Group' field to the ticket assignee's name in JSM? 

[Sachin Dhamale]

Does it support multilevel cascading or only 2 level?

[Rodney D_Souza]

@Urmo For Asset type fields there already has been a way to create cascading relationships using "Filter issue scope (AQL)".   I use that a lot and so this new capability is probably for simpler scenarios and when folks do not have Premium license for JSM Assets.   If you want further explanation, you can let me know.  Thanks

[Michiel Schuijer]

Nice!

[Evaldas]

So, basically, it's the same functionality as the custom field with type "Select List (cascading)" already had, but now put in a Form (and added an small feature - "Required Parent/Child choice")?

Thanks, I guess... but why don't you implement features we don't already have and that are highly voted?

[Sam Knight]

Hi all - thanks for your feedback and questions!

- This was a top 5 voted JSM customer suggestion - and we can see a lot of you are using this already which is great to see!

- There is not currently a way to have the validation applicable to the child, though you can specify that a certain child is selected (e.g. a specific child option choice)

- Assets is not currently supported, but we will be making big investments in how Forms integrates with Assets in the coming months given how important Assets is to high maturity service delivery

- We only support 2 levels to align with the Jira Cascading Field type

Thanks again for your support!

[andrew_pass]

Hi @Sam Knight 

This is great and super useful, are there any plans for making the child required?

Otherwise as useful as this field is it'll be fairly pointless as most users won't bother selecting a child so any conditional sections with information relevant to those won't be captured.

Thanks,

Andy

[Julian Governale]

Hi @Sam Knight Is there any feature requests to enforce that the child value is required?  If not can one be created?  

[Daniela Tieber]

Hi, it would be very helpful to have the option to make the child value a required field! Thanks