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

Jira Automation Efficiency

I have several global automation rules that work as expected.  However, due to the volume of tickets in the project, the automation rules run hundreds of times a day.  Therefore, we are quickly maxing out of number of global automation rules permitted.  Is there a way to re-write these rules to make them run less frequently?


1 answer

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 04, 2023

There's no way to reduce the number of triggers without changing how your users work.

But you could merge the automation - the "if value of field X changes" doesn't have to be one per field, you can say "if the fields X, Y, or Z change".

Also, the middle rule you have only works in one project.  You could remove the project check from it, and put the rule into the project instead of it being global, so it wouldn't count against your global automations any more (and wouldn't even start for anything other than that project)

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 04, 2023

Hi @Alexandra Astor 

Adding to Nic's suggestions...

Without seeing the details of your rules' issue edit actions, I wonder if the edits of the two merged rules could be done with one branch and one issue edit action.

  • The branches are different (one is on "clones" and the other is on "clones" or "is cloned by") so perhaps they need to be separate, but if not that would reduce processing time.
  • Another processing improvement could be to use the JQL branch to check for linked issues of a certain type and in QMT in one step, rather than with the linked-issues branch plus a condition on project.
  • With one branch the edits to fields might be done in one edit step, if you do not worry about them showing up in the history as changes when not necessary

Finally to Nic's original point, knowing why the first two rules are needed may reveal other alternatives.  That is, what problem are these trying to solve?  I hypothesize you are doing this to help with reporting and issue alignment on roadmaps across projects.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events