If a cascading select field is set to required, only the first selection field is actually required. The second field can be left unselected. How do I make both fields required? I found this:
cfValues["myCascadingSelect"]?.getKeysAndValues()?.size() == 2
but have been unsuccessful in getting it to work as a validation on the create transition.
We are running JIRA v5.2.5
There is a similar question regarding on this posted before, perhaps you can refer on this as a general guideline and reference : https://answers.atlassian.com/questions/17148/workaround-solution-for-making-2nd-drop-down-required-in-multi-cascade-custom-field
Hope it helps :)
I tried it in a workflow transition validator (using the option 'Simple scripted validator') and it does not seem to work.
I read in another post that since Jira 5.x, the values are returned as a map, so they suggested this check:
cfValues.get("customfield_17637")?.keySet()?.size() == 2
but it does not work for me (meaning when I put a not-None value, it still fails).
I am trying to implement this , however I get the same error.
My requirement is a bit different however. I want that second field of cascading select field is mandatory only if the first field is not empty.
Is anyone able to implement this successfully?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs