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 can I set up the order to run the rules in Jira Automation?


I have 3 rules with the same conditions to create tasks for created new epic (trigger).

There is a need to have those tasks in a particular order to make it more readable in the epic.

How can I set the sequence to run the 1st part then 2nd part and 3rd part?

I cannot combine tasks because there is a limitation in Jira on the quantity of actions/tasks in one rule. 

Right now I get a mess of tasks from three rules. It is very difficult to see what should follow what.


Or is there a way to move tasks inside the epic to correct the order.

I understand that it is possible in a backlog view, but there is a need to have the right order in the epic itself.






1 answer

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 01, 2020

Hi Natalia,

There is not current a concept of delaying executions of rules in Automation For Jira. You should possibly set it up where one rule files and at the end of the rule it sets a value in a custom field. Then rule number 2 will look for the value of the custom field getting changed and then fire. Then do the same with rules 2 and 3. 

Like John Funk likes this

@Natalia Golikova did this work for you? can you please share screen shots of if you were able to make this work?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events