Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to make mandatory only parent fields in a cascading field during issue creation

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.



2 answers

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:

  • Add a Logical Validator in your "Create" transition, and use the following expression if you want to make mandatory the parent value:
    %{issue.cfAAAAA.0} != null

Where AAAAA should be replaced by your cascading custom field code-

  • If you want to make mandatory the child value, then you should only change the 0 and write "1" instead, just like in the following example:
    %{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,

0 votes
Darryl Lee Community Leader Dec 02, 2022

So by default, if you make a cascading select field required, it only makes the parent required. Here's a bug that confirms that:

To make child fields mandatory, that will require an add-on that provides a custom Workflow Validator, such as one of these:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events