Hey all - happy to share that Cascading fields are now available for all instances (except for Release Tracks customers, which will be in the November bundled release)

Thank you to everyone who voted and shared context on why this is so important!

Sam

JSM Principal Product Manager

bf42a8bebb74 The "can't make the child mandatory" problem extends beyond forms - you can't apply it to the normal Service Desk customer request type (or presumably in normal Jira screens). 

It's covered in this page:

https://community.atlassian.com/t5/Jira-questions/How-to-make-both-fields-required-in-Cascading-Select-field/qaq-p/1019465?utm_source=atlcomm&utm_medium=email&utm_campaign=kudos_answer&utm_content=topic

The solution mentioned there might not apply to forms though

It would be great if it was possible (built in) though.

Good to see this implemented.

Problems with the current implementation:

• When making the cascading field required, there is no way to make the child selection also required.
• Also default selection for the child selection per parent would be needed.

This is a great addition, and I am already taking full advantage. Looking forward to more updates to the forms - I agree with the latest comment, an update to sections and how deep they can be conditional would be amazing. 

Thanks!

Great news! Now please give us section conditions like "IF field_x IS EMPTY" and "IF field_x IS NOT EMPTY" please.

Cascading fields are now available for all instances (except for Release Tracks customers, which will be in the November bundled release)

Umm, I need this for yesterday please.

Sorry for beating the dead horse, but releasing form fields and not releasing a simple cascading field is a very dumb idea. Then releasing it for Premium users is mean.

We're talking about releasing a field that is already pre-historic given that Atlassian should already be supporting multi-level cascading and also multi-select cascading which I think there's hope those would perhaps be released in 2084-ish by the way things move at Atlassian when it comes to fields.

Enough said.

Don't hold your breath, and wait until you see the actual implementation before you let out that sigh of relieve. 

Update, please???

Any Update on this feature 

Update, please?

Our customers love forms until they find out about the strange limitations which can't be that hard to fix for an average developer.

Forms are THE major feature of Jira Service Desk and a big selling point or would be if not for some of these odd limitations.

f.e. no cascading fields, no IS (NOT) EMPTY for section conditions (especially for Jira Assets), no multi-field section conditions, forms complaining about summary being inside a condition, no easy way to transition from a normal request type without forms with many fields to a request type with a form unless manually reconstructing it from scratch, very limited in what Jira Assets attributes can be displayed, spacing between normal Jira request fields and form fields is always slightly off, no forms for software projects, and so on.

Update May 2023

This is not on our short-term roadmap; however, we are considering it in our plans for the first half of 2024. We will provide another update on this in October 2023.

Thanks,

Simon

JSM Principal Product Manager

And we are almost at the end of first half of 2024. Would you care to give us an update?

We cannot use the Select List Cascading field type in the Form and build conditionals because it is not compatible.

We can use Assets fields and simulate a "Cascading" effect in the Form, but the value of the dependent field is not automatically removed when the value of the master field is changed JSDCLOUD-10496.

In other words:

There is currently no way to safely use the Cascading model in Jira with conditionals applied, and this is frustrating since the issue is treated as a "suggestion" rather than an essential item to be prioritized.

The only way to safely use a cascading field today is by using the Select List Cascading field in the standard Jira form. However, it will be a static form, and you cannot use conditionals.

We pay so much money to Atlassian, while simple bugs like this sit around for years.... 

Please fix this guys. 

HELLO - anyone out there?? An update please!

If Atlassian is thinking the workarounds are sufficient - that is not the case.

The suggested functionality is only available with JSM Premium/Enterprise.

Need the cascading list funktionality

Consider my interest gathered.

I have always find it hilarious that:

1. Jira is a system that helps you to keep track of issues and bugs.
2. Atlassian lets issues and bugs fester for years and even decades.

It doesn't help that nobody from Atlassian is looking at the form bugs and requests. The person they've assigned these to hasn't been active for 6 months!

Our team cannot use Forms without being able to use cascading fields. They are used across our organisation by multiple projects and are reported on. It's odd that now in-built functionality (Proforma) does not support a Native Atlassian field type (cascading fields).

We're currently using an add-on from Deviniti for our request types. This needs to be paid for and completely lacks any of the Confluence editor features, such as info panels. For our most important forms this lowers the user experience, as help-text for fields in our Add-on is tiny and often missed.

This feature would be greatly appreciated.

STILL WAITING!!!!! 

Is any feedback expected on this issue? Six months have passed since the promised date of feedback, but there is still silence.

This is the most voted request related to forms, but it is being ignored. Please take this request in work already.

Also, the assignee is inactive, as mentioned in the comments, which is doubly funny.

why did you leave behind such a simple custom field? Are you planning to remove it from our instances? if not it seems to me illogical to exclude it from forms.

Now if I need a cascading custom field to be filled in my form, I have to create another field, a select list custom field, whose choices, through an automation rule, are going to select to corresponding ones in my cascading field. 🤯 fix this bug thanks

Atlassian: Jira is a software used to help developers keep track of issues.

Also Atlassian: 

EDIT - Also, Simon left Atlassian months ago but still as 61 issues assigned to him that no-one is picking up. Someone should do something about that right?

I guess they must have exceeded the automation limit so the issues can't be reassigned.  

An update was planned in October 2023.

I know this ticket has changed assignee but Atlassian should still honour some kind of communication schedule for requests that are actually on a roadmap.

An update of 'no progress' is better than ignoring the silence.

Please provide an update.

EDIT - Also, Simon left Atlassian months ago but still as 61 issues assigned to him that no-one is picking up. Someone should do something about that right?

Please can you add this, it's a fundamental functionality in a form editor :/

This feature is critical in our company.

Waiting for this

Pleaseeeee

Why this is still in Gathering Interest?  Atlassian owns the FORM now, which should support its own field type: Cascading field.  Come on, Atlassian!

Adding this default Jira feature will further unlock the potential of the Forms feature. We already have to introduce more custom fields and complex automation to our environment which we will have to remove once this feature is released. The longer your customers do not have this feature, the more technical debt will be accrued over time, please consider this for 2024!

This is a must comon guys!!!

Defiantly need this one. 

Do this. It's not even a feature. This is basic product functionality that is hobbled for forms users.

This would be fantastic and would prevent me from having to do a whole lot of redundant work!

please. 

Please help!

Implement asap please

Must need feature!!!

This would be a very desirable feature

The cascade field should be there. It will make the forms round about perfect.

This is weird why Atlassian not adding support of cascading field in dynamic form.

I'm now blocked due to this when migrating our from from a 3rd party plugin to the native form feature.

Is there anyway Atlassian can expedite it? 

+1

I need this

Please implement it!! It can help us a lot 

I need this, to improuve my formularies! Help Us !

This is a thing I always hear from my clients. It would be extremely useful

If you are fortunate enough to be running on Jira Premium, they just implemented asset fields in forms within the last few weeks. This can give you a similar affect of being able to use cascading fields on forms. Its a decent workaround until this is fixed. 

A must !
 We are not able to create the form we desire because of several cascading fields.

Could you please provide an ETA? :pray:
 
 
 
 
 

absolute must to have this feature.. section based conditional blocks are just starting point

How could you miss this option? At least needs to be at parity with your own features

is this feature on the JSM roadmap? Would be extremely useful to allow cascading fields in JSM forms like it exists in Jira.

Hi Simon, 

Can you please tell us when this will come. The things is we are implementing JSM in Facility Management and we need to use Forms but this function stop us. 

This is very important feature to us. We have a lot of cascading fields.

We use the cascading fields in 90% of our projects and with it we have managed to create several automations based on the "second level". This field is really a facilitator since we don't need TWO single list fields to reach the same result.