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
4,365,853
Community Members
 
Community Events
168
Community Groups

Automation - interfering other rule

Team

 

I have set the rule for automation - ticket assign to Region - Location - Assignee. In UAT it tested successfully.

But after moving to prod rule has been interfering other rule. For example. Ticket assigned to correct person later moved to another person automatically not sure how to solve this.

 

 

2 answers

1 vote
Rilwan Ahmed Community Leader Sep 23, 2022

Hi @Lakshmi Narasimhan ,

Seems one more automation rule is getting triggered. To know which rule is getting triggered, then click on Rule Executions.

To make sure the triggers are not overlapped with other rule, make use of JQL conditions/Issue fields conditions or other available conditions in both the rule to get them differentiated. 

1 vote

Hello @Lakshmi Narasimhan

This sounds like familiar behavior. It happens in our instance as well when we have automations that trigger on the same event, or within the same timing window. Unfortunately we have yet to find a way to prioritize the order in which automations are triggered, or to have them wait on each other. 

The solution we are using is trying to find other triggers. Perhaps you can trigger on a field being changed instead of an issue being created for example.

It requires a bit of trial and error I'm afraid. If someone else has a better solution, preferably with native Atlassian functionality, then please take their advice.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events