Could you automate code reviews in more than one way?

[Shaherbano Mirza]

My team needs an automated code review process.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

Block if:
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'

[Eliot Andirson]

hey 

 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