Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Automation rule timing out on large board

John Ackerman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2026

Hi everyone,

We’re having an issue with a Jira Automation rule that transitions issues when a label is added. It works fine on smaller boards, but on our largest board it often times out or doesn’t run at all.

We’ve already simplified the rule and tested it elsewhere with no luck. Has anyone experienced this, or are there best practices for automations on large boards?

Thanks!

2 answers

2 votes
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 Champions.
January 22, 2026

Hi @John Ackerman -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

  • What problem is your rule solving?  That is, the "why".
  • What version of Jira are you using: Cloud, Server, or Data Center
  • For Cloud, what type of space / project is this: company-managed, team-managed, JPD, JSM, etc.
  • An image of your complete automation rule in a single image for continuity
  • Images of any relevant actions / conditions / branches
  • An image of the audit log details showing the rule execution, both working as expected and not
  • Explain what is not working as expected and why you believe that to be the case 

 

Kind regards,
Bill

0 votes
Philipp Sendek _catworkx_
Community Champion
January 22, 2026

Hi @John Ackerman and welcome to the community,

Automation rules always should run in the background and should generally be independent of boards or other UI elements in Jira. What exactly is the automation doing? Is it just transitioning a work item or is it also doing something in addition to that?
Also, can you see from the audit log of the Automation what's taking it so long? Does it take long for it to start it or the transition its executing?

For Automations it does help when you place the "Log action" (Not log work) including some senseful text like "Starting action xyz", "Finished action abc" before and after every key action element within your Automation rule. That way, when you look at the audit log of an Automation, you see how long it took between the steps or if something was skipped (and the log action wasn't triggered).

If you provide these additional infos, we should be able to get closer to the root of this.

Greetings
Philipp

Suggest an answer

Log in or Sign up to answer