What happens if you have to update issue assignment from automated Round-robin assignment?

[Jasmin Rizko]

Follow up question on Round-robin issue assignment for Jira issues.

Let's say we have Users 1, 2, and 3 in the list.

Ticket 1234 is filed and auto-assigned to User 1. However, User 1 is on PTO therefore the ticket must be manually reassigned to either User 2 or User 3.

If ticket 1235 is filed subsequently, will it be auto-assigned to User 2 because initially ticket 1234 was assigned to User 1? Or will Jira refer to ticket 1234, get the assigned user, and then increment?

[Bill Sheboy · Accepted solution]

Hi @Jasmin Rizko 

Are you performing the assignment with an automation rule's Assign action?  If so, it appears round-robin uses the sequence of users in the list/group and thus would select User 2 in your example.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Assign-issue

Kind regards,
Bill

[Jasmin Rizko]

Hi Bill, yes automation rule's Assign action based on Issue Creation trigger. Thanks for the speedy reply, this is very helpful!!

[Bill Sheboy]

Pondering this a bit more, it would be possible to make this adjustment to assignment auto-magic by either:

• Create a separate group which you update, and it only includes the people currently available for assignment.  Then update the rule to use that group.
• Create a separate group for people who are out-of-office/cannot be assigned.  Then modify the rule to be a bit more sophisticated.  Note this could take several seconds for this rule to run.
  • Call the REST API with a web request to gather the "all possible assignees" group
  • Call the REST API with another web request to gather the "out-of-office" group
  • Remove the second values from the first list
  • Perform round-robin assignment based on the result...if there is anyone available to assign

[Arianne]

How do we do a round-robin assignment via rest api?