We created a group of users, and set the project automation rule to assign new issues to members of this group, in round-robin fashion. As long as the group remains the same, the assignments appear to be in alphabetical order by the names of the members of the group. But when we add or remove members from the group, this can have unpredictable effects on the order of assignment. Sometimes, after removing a member and adding a new member to the group, the automation rule will start the round-robin over with the very first alphabetical order member of the group. Other times, it will assign the next issue to the last-assigned user in the group.
We worry that if we regularly add/remove users to the group (to account for agents who are in/out of office), then the project automation issue assignment round robin rule will keep resetting itself at the alphabetical start and people with earlier alphabetical names will end up being assigned many more tickets than people with later alphabetical names. Can you clarify how the round-robin assignment rules work, in situations where members of the group are added/removed/changed? Or is there a better way?
Hello everyone! We are very excited to announce some much needed changes to the issue create experience in JSM (the blue "create" button) at the top of the screen. We have just starte...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events