You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The code review process involves two rounds, and I would like to automate sends to either our frontend or backend developers.As an example, a ticket would be assigned to Frontend group A when it gets moved from the In Progress column to the First Code Review column. Following the first code review, the ticket gets assigned automatically to group B of frontend developers and moves into the 'second code review' column.
Backend tickets are handled the same way.
Do you think this is possible? Backend developers are assigned tickets time and time again. The current setup is as follows:
The status of this issue has been changed from IN PROGRESS to CODE REVIEW
This issue will be assigned via Round Robin To (a list of users of Group A developers)
The issue data needs to be re-fetched
Comparing [[issue.assignee.name]] with [[issue.reporter.name]] in advanced mode
Developers in Group A are the Users Condition Assignees
Round Robin To (an email list of Group A developers) assigns this issue to 'A User Defined List'
Recommended Learning For You
Level up your skills with Atlassian learning
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Managing Permissions in Jira Cloud
Sharpen your skills at configuring and troubleshooting permissions in Jira Cloud with this free course.