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; } } }

cascading drop down incompatibility

Bernard Clabots

Hi,

I made a form where I have a first selector for country, then a cascading choice for unit.
All was fine for almost 2 years, until we decided to make this field mandatory.

1. When mandatory, it is OK to select just one level and leave the other empty. I see no possibility to enforce both levels

2. Slack integration is broken as soon as this field is mandatory.

3. While working for a work around, I figured out automation does not support this field.

Are there any plans to fix any of these? If at least it would work with automation, I could split the field in two fields that I make mandatory, then I update the cascaded field accordingly. As I wrote, we used that field from day 1, so I can't just split to 2 new fields as filtering e.g. will not work with older records.

Accepted answers

Nic Brough -Adaptavist-

Yes, there's a long-standing known flaw with this field type:

Atlassian have had this on their to-do list pretty much since cascading fields arrived in Jira (Well before Cloud was forked off). It is still open, so they've not ruled it out, but we're still waiting to see any progress
This isn't so much to do with the field, it's more that the Slack integration can't handle mandatory custom fields
Automation is limited in how it can work with the field, yes. What exactly were you trying to do that it has failed you on?

All comments

Nic Brough -Adaptavist-

Yes, there's a long-standing known flaw with this field type:

Atlassian have had this on their to-do list pretty much since cascading fields arrived in Jira (Well before Cloud was forked off). It is still open, so they've not ruled it out, but we're still waiting to see any progress
This isn't so much to do with the field, it's more that the Slack integration can't handle mandatory custom fields
Automation is limited in how it can work with the field, yes. What exactly were you trying to do that it has failed you on?

Bernard Clabots

Regarding 3, just trying to copy the value from another field to the cascading drop down, so I could circumvent the issue.

Nic Brough -Adaptavist-

You can only copy the value of a field between fields of the same type and content. With a cascading-select, this means you can only copy a value when you're going to the same field on a different issue!

Cascading fields don't actually have two parts, when you look in the database, there's a single value stored!

And, as you've found, Automation has not yet been written to understand that.

You'll need to use one of the scripting apps that can support code to read them in the way you want to use them.

Monika Marko

Has this issue been resolved? Did Atlassian figure out a way on how to ignore the slack inability to read mandatory cascading custom fields?

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