Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation - Assign a different person in a status and reassign back when status change

Deleted user April 20, 2022

Hi guys, 
Here is the scenario:

We have 5 developers in our team

  1. Developer A move issue to "DEV WIP" and assign him/herself
  2. Developer A then change the status to "Code Review" and Jira assigns another Develper randomly (but not the original Developer A); let's say Developer B
  3. When Developer B change the status to "QA Pending" (or any status really), Jira assigns it back to Developer A (who moved the issue to "DEV WIP" and assigned him/herself).

I've set up 2 rules in order to make this scenario happen:

[RULE 1] Trigger when the status change to "Code Review"

 Screenshot 2022-04-20 155853.png

[RULE 2] Trigger when the status change to any other status

Screenshot 2022-04-20 160100.png

Now I have a problem which I cannot find a solution to at the moment... Since it is randomly assigned to a list of developers, there is a chance that it will assign to the same developer.  and it happened sometimes and we have to manually fix it. 

I have an idea that I can set a condition that checks if the automation assigns to the same assignee, and if it's true, then re-assign another person again until it's a different person; but I don't know how to implement this idea.  

Is there a better way in the Automation setting that it will skip the same Assignee?

Thanks!

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 20, 2022

Hi @[deleted] -- Welcome to the Atlassian Community!

With the built-in features, I believe you would need to change from Random to Round-robin assignment.  At least that would help also reduce the chance of Random overloading one/a few Developers.

A more convoluted (and slower) work-around would be to use list-based assignment and remove the current assignee:

  • call the REST API to get the people in the Developers group
  • convert the list of people's accountId values into a list
  • use smart value list filtering to remove the assignee
  • use that resulting list as the source for the Code Review assignment and still use Random

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events