Can we restrict automation rules which one will run first?

[Umar Maroof]

Hi 

I have 2 automation rules. 

Rule 1: once the task 1 goes to status done it will create another task (name task 2)

Rule 2: When all tasks under epic status= done change the epic status.

Problem:

When I make task 1 done rule 2 runs and change the epic status and then rule 1 creates the task 2 which is not in done status.

I want rule 1 run first and create tasks 2 now when task 2 also= done then rule 2 runs and change the status of epic.

Because this is just example I explain otherwise I have  4 5 tasks which creates new tasks as well once they done so I want the rule 2 will run when all the task under epic will goes to done either old or the new once which are created by rule 1.

[Walter Buggenhout · Accepted solution]

Hi @Umar Maroof,

The short answer is no. Automation rules respond to events that are triggered by things that happen in your Jira instance. When you work together with many people in different projects doing all kinds of updates simultaneously, things get complex.

You seem to have built a scenario that is bound to introduce potential conflicts. What you may try to do is redesign your automation rules to reduce the chance of these conflicts occurring. 

You may want to consider using a scheduled trigger to close (and - why not - reopen) your epics in bulk once or twice a day instead of reacting to every status update of an issue. That will reduce the chance conflicts occur and even automatically fix epics that were closed unintentionally; 

Hope this helps!

[Umar Maroof]

@Walter Buggenhout Thanks Thats helpful.