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:
Hi @katie.kurty -- Welcome to the Atlassian Community!
Would you please post an image of your automation rule(s) and the audit log from executions? That may help the community give you ideas by providing more context. Thanks!
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.