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 prevent transition to done on Epic if it has open issues under it, using Jira automation?


I would like to set a transition condition/validator using automation, if Epic is move to done status, check the linked issues in this epic and fail the transition if any of the linked issues are not "done". 

The same as "linked issues status validator". can I use Automation to create such rule?

I'm using Jira cloud




3 answers

0 votes
wwalser Atlassian Team Feb 09, 2021


Just chiming in as a member of the Automation team. Agree with others here who have noted that Automation is not able to create a great user experience here because we can only hook into the action _after_ it's happened. I don't think this falls into a natural use-case for Automation for the moment. Workflows or perhaps a marketplace plugin feel like the way to go here.


0 votes
Curt Holley Community Leader Feb 08, 2021

I agree with @Darryl Lee regarding "real time" is better than post assumed success.

That said, i helped a team set up automation at Story level to monitor for sub-tasks still open and just sent the "initiator" (the person who did the transition) an email.

automation 2021-02-09 123405.png

0 votes
Darryl Lee Community Leader Feb 07, 2021

Yes. A former client implemented such a rule.

The trigger was the initial Transition. There was then an IF block to see if the linked issues were not Done, and if not, then it was transitioned BACK to the previous step.

I believe the rule also added a comment to explain why the transition was "rejected".

Darryl Lee Community Leader Feb 07, 2021

Oh, I should note, while this will work, I'm not a fan.

While it's unfortunate that you'd have to pay for a third-party add-on to implement this as a Validator, I it's a much better user-experience to tell users that they cannot do something when they click Submit.

Letting the transition succeed and then notifying them afterward (by the comment) doesn't seem very user-friendly.

Like petre mierlutiu likes this

Thanks for your answer, I'll try that with comment when it's rejected. I agree it would be better to do that as workflow validator.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events