I'm trying to create an automation for my team's code reviews. We do 2 rounds of code reviews and I'm trying to set up automations to go to either our Frontend developers or Backend developers.
For example, a ticket comes in and when it gets moved from 'In Progress' to 'First Code Review' column it would get assigned to group A of Frontend developers. Then when the first code review is completed the ticket would then move into 'Second Code Review' column and get auto assigned to group B of Frontend developers.
And then the same for Backend tickets.
Is this possible? Tickets keep getting assigned to Backend developers. Here is how I have it set up currently:
Thanks for that screen image, @katie.kurty Some follow-up questions...
You note two code review columns on your board, First Code Review and Second Code Review. Which status values are mapped to those columns?
Your rule shows a trigger from In Progress to Code Review. Later you check if the status is FE First Code Review. How could that condition ever pass as the trigger says you are in "Code Review"?
And...if you indeed have two code review columns and two code review status values mapped to them, do you have 2 rules, one for each possible transition?
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
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