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

What is best automation solution? Multiple rules or multiple conditions?

I'm creation automation for a project pipeline, changing the task status when subtasks change status.

I currently have one rule for each status, and everything works as designed. But something that I can stop thinking about is: what approach has a better performance? Creating multiple rules as I did, or creating a single rule with multiple conditions?

I'm asking it because I feel the tasks are taking a bit longer than I expected to.

1 answer

Hi Rubico,

I've found a page regarding performance of Automation, although from 2018 before Atlassian acquired Automation for Jira it is still worth a read:

They do recommend to combine Rules where possible. But at the end of the day it is your choice.

In the audit log of each rule it gives a duration, so you can see if there is hold up somewhere or to test if making changes does impact speed.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events