Team Collaboration for Code Review › How the Review Request Works

How the Review Request Works

In general, you create one review request for a given package. In some cases, each individual who has a part of the code changes for the given package creates a review request, resulting in multiple review requests.

The CA Harvest SCM server maintains the status (Open or In Progress) of the Peer Review. When you create a Peer Review, its status is Open. During the life of the Peer Review, when reviewers make any Votes, Comments, or Attachments, the server changes the Peer Review status to In Progress. If all Votes, Comments, and Attachments are deleted from the Peer Review, its status is changed back to Open.

The steps for processing a review request are as follows:

1. As the review requester, you create a review request for the contents of a package. You invite one or more users in a project to participate the code review. You designate one user as the primary reviewer.

   Note: The primary reviewer determines the final result of the code review. The vote decided by other reviewers is for reference only.

   You can set an option to send email notifications to all the reviewers and requester. The emails inform participants of their review request assignments and of any updates to the review.

2. A reviewer can double-click the version associated with a review request to open the Review Comments Editor to view the changes in the selected version and enter comments. Reviewers use this editor to do the following:
   • View the changes in the new version and compare the changes to the parent version or another selected version.
   • Add comments to any line of the version for review.
   • Insert multiple comments at the same line by one or more reviewers.

     While these comments can express support and suggest improvement, typically the comments identify problems, issues, or concerns. The comments can support or identify why the reviewer did not approve the package changes.

   • Add attachments to any line of a version for review.

   All reviewers can vote Yes or No for a review request. By default, the status is shown as pending for each reviewer in the review request. The vote indicates that you approve or disapprove the changes for the entire review request. When an approve package process exists in the current working state, the primary reviewer can also approve the package during the closure of review request.

   Note: The Approve Package option is enabled when the Vote is Yes from the primary reviewer. In addition, before you can use this option, an approve process must be defined. The primary reviewer must belong to the approval group with execute access granted to the approval process. For more information about defining the approve process, see the Administrator Guide.

More information:

Reviewers

Create a Review Request

Review and Add Comments

Vote on a Review Request