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!
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:
Kind regards,
Bill
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.