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

Automations conflicting

We have a few automations, we only started to use Jira in July and have found some of the automation are conflicting with each other.


For example, we created an round-robin automation for the service desk queue.

We have other automations to say if the sender or subject is this assign to another agent queue with the assignee assigned.

We are finding, some tickets are being assigned to the right group, but the round robin automation is assigning to a service desk assignee.

open for suggestions.

We have over 50 automation so combining them is not an option

1 answer

3 votes

Hi @Danielle David and welcome,

I'm not aware if an app exist for tracking conflicts of Jira Automation. You could search for something in the marketplace. However my advice would be to try and document all your rules. 50 rules are a lot and if no documentation exists this makes it more hard to know what's going on.

My advice would be to look at the general audit log and try to understand what's going on. Which rules are running together. Group them and seek any conflicts. Then try to amend them, merge them, or document them.

Hi @Danielle David -- Welcome to the Atlassian Community!

Yes, what Alex suggests:

I do not believe there is much available yet for management of automation rules.  And these things are "code" in an project/instance-scale solution without source control or a release pipeline.  To me that means I should treat them as such:

  • figure out a way to effectively review and test them (e.g. peer review, pairing, etc.)
  • figure out a way to document rules (e.g. export, Confluence, etc.)
  • figure out a way to version control rules (export and store the critical ones in a version-control repo)
  • figure out a way to monitor their health (adjust the alerting for rule errors to email a distribution list, and/or consider sending notifications for *all* errors and not just the first n-count, which is the default I believe)
  • add a few global rules to watch for SLA violations, based upon your license limit.  Just one run-away could use up a site's limits for a month.

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events