Global automation versus project automation.

[Jarmo Parviainen]

Does global automation always overrun, project automation or can this be configured?

[Bill Sheboy · Accepted solution]

Hi @Jarmo Parviainen 

What do you mean by "overrun"?

Automation rules are triggered by events (e.g., issue created).  And rules have "scope" of a single project, multiple projects, or global (all projects).

And so if the event happens, the rule runs, regardless of the rule scope.  An exception is when Atlassian has an outage of Jira or automation features.  Some rules may not run as expected in those cases.

Kind regards,
Bill

[Jarmo Parviainen]

I have project rule for creation of epic description and then global rule for the same action. It seems that when I create Epic the project rule is run first then the global rule overwrites the description. 

Ok but this seems to be fixed now in our environment. One condition added to global template "if description is empty". They both are still run but no more overwriting. 

So all good now :)

Thanks for the reply anyways.

[Bill Sheboy]

If two or more rules have the same trigger (e.g., both on Issue Created) covering the same scope (e.g., one global and one project rule), I hypothesize the order of execution is unknown and it cannot be relied upon to order actions.

If instead one rule does something (e.g., a rule action) that could trigger another rule, that ordering can possibly be managed.  This behavior is disabled by default to prevent rule errors and looping; it can be enabled with the "Allow Rule Trigger" option in the downstream rule's details.