You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are using DC jira
1)How to make mandatory only parent fields in a cascading field during issue creation
2)How to make mandatory only child fields in a cascading field during resolution.
Could you please help on this requirement.
Regards,
Prasad
Hi @prasad Biddika ,
I'm Sergio, from Decadis. As Darryl Lee indicated you before, this functionality can be achieved using our plugin Jira Workflow Toolbox.
You would only need to do the following step:
%{issue.cfAAAAA.0} != null
Where AAAAA should be replaced by your cascading custom field code-
%{issue.cfAAAAA.1} != null
I hope this information is useful for you. If you have any other doubt related to our plugin, we recommend you creating a ticket in our customer portal site.
Thank you.
Best regards,
Sergio
So by default, if you make a cascading select field required, it only makes the parent required. Here's a bug that confirms that: https://jira.atlassian.com/browse/JRASERVER-21383
To make child fields mandatory, that will require an add-on that provides a custom Workflow Validator, such as one of these:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Found a ScriptRunner example here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.