Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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,459,081
Community Members
 
Community Events
176
Community Groups

Service Desk Automation Rules - setting the assignee

We have a group that is needing to automatically set assignees based on the statuses of one shared workflow. The assignees differ per customer request type. The current automation rules are configured per customer request type, but it doesn't always work correctly. In some cases, Jira will use the wrong automation rule to set the assignee, then correct itself. But the incorrect assignee still gets an email notification, of course. We have tried altering the JQL, but no luck.

I am thinking about changing the automation rules to be configured per status, and not request type. This way, Jira only has the read the automation rule per status and not have to check all the individual ones per request type. 

Anyone have any experience on this, or tips on best practices with automation rules in service desk?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events