If we perform code reviews, we do that per branch. We would therefore like to see only the reviews for changes that originated in the current branch.
Code review for current version.
Software Factory
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Best practice is to have all control procedures reviewed before they are merged to the trunk. A new branch would always start with no control procedures in review.
As long as that is not the case, should that version of the template be merged, or do you want to revert to the previous (reviewed) version?
A practical workaround can be to turn the statement around: "This code is being used in production, sure it is ready for review". That allows you to bulk set all control procedures to "Ready for review" at the start of a branch, with an appropriate change log description. It does mean that some old code will never get reviewed until there is a new modification of the control procedure or until those control procedures with that description are demoted to a development status.