This question is in reference to Atlassian Documentation: Adding a Custom Field
I have created a cascading custom field and made it mandatory, but it allows to skip the second/child list which should not be the case.
Please let me know how can I achieve this, so that child list is also mandatory when the field is mandatory
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events