I have a cascading select field in which a couple of options in the first field have no further options in the second, but a few do. The whole field is marked as required.
There are a couple of options for this field to be filled:
Situation 1: Field 1 = Not filled, Field 2 = Not filled
Situation 2: Field 1 = Filled, Field 2 = No options, so "None"
Situation 3: Field 1 = Filled, Field 2 = Multiple options, one is picked
Situation 4: Field 1 = Filled, Field 2 = Multiple options, but "None" is picked
When adding a validator in the form of "Cascading select field != EMPTY", situations 1 through 3 will be fine. Situation 4 is weird, since that will fail the validator even though Field 1 is filled. So if there are options in the second field, you have to pick one, even though that's not necessary when there are no options in that field.
How can I work around this in the validator?
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG