We have added a new status in our workflow called Code Review that is triggered when we change the status from In Progress to Code Review and before Work Completed. On the transition screen, we have created a custom field (user pickler- single user) called Code Review Assigned. The idea is to have one of the senior developers or dev management review the code for the developer. We do not want to override the original assignee field so that we know who the developer working on the ticket is.
Expected Behavior: We would like the Code Review Assigned to receive an email when they are assigned. We do not want to default to one person because there are many different people who can review the code depending on the issue.
We couldn't find automation that allows this, now could we nor a post function in the workflow.
Any thoughts on how to do this?
Please advise and thank you in advance.
You could use a combination of JQL and our app Notification Assistant for Jira for exactly this. Set your custom field as the recipient, and then adjust the JQL to limit the notification to the right tickets. Then set the trigger as Field Updated and pick your code reviewer field.
An alternative to this is to have people pair with the senior engineers until everyone in a dev role can review anything, making this much simpler to do... For your specific question:
There is an open suggestion in the backlog to support your use case: https://codebarrel.atlassian.net/browse/AUT-273
Until something like that gets implemented you could try some more complicated work-arounds with automation for Jira rules:
Re-use the assignee field temporarily
The re-fetch is key in order to get this to work.
Manually re-create round-robin assignment (if you have only a few reviewers)
Both of these ideas have a lot of moving parts, so if you try them I suggest writing to the audit log a lot for testing.
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.
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.