Back to Part 1
Action: Request a Review
Although the code review feature is work item-based, you cannot create these work items as you would a User Story or Task. There are two means to initiate a code review:
1. Requester must have some pending changes in order to request a review.
2. Requester selects a committed changeset from Source Control Explorer.
NOTE: Because I believe it will be the more popular means of requesting a review, the first method is the workflow this post will focus on.
In My Work, under In Progress, click the Request Review hyperlink to navigate to the New Code Review pane.
The reviewer must enter at least one reviewer, but he/she can enter as many as they would like.
Requesters can also choose from a list of recent reviewers by clicking the arrow next to Add Recent Reviewers.
The Subject field will default to the Title field of the In Progress task, but it can be edited to provide more clarity.
The Area Path field can be used to associate this code review with a particular team, product, or component.
The Description field is not required, but it can provide some guidance to reviewers to ask a question or focus on a particular area.
Notice the code review is already associated with the In Progress work items to provide additional context to reviewers.
Don’t forget to click Submit Request before navigating away from this pane!
The pending changes will be automatically shelved.
At this point, a Code Review Request work item is created with the Title field matching the Subject entered. The initial State will be Requested with a Reason of New. The Assigned
To field will be the requester.
Child Code Review Response work items will be created for each selected reviewer. They too begin with a State of Requested and a Reason of New. However, each work item’s Assigned
To field is set to the name of the reviewer. At any point in time, the requester can add additional reviewers too.
Proceed to Part 3