Edit

Share via


Code review and feedback field reference

Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022 | Azure DevOps Server 2020

This article lists the fields you use to track code reviews and feedback, including descriptions, data types, and recommended uses. Use these fields to build queries and reports that monitor code-review and feedback workflows. The default work item types that include these fields are: Code Review Request, Code Review Response, Feedback Request, and Feedback Response.

Fields used to track code reviews

You can only make a Code Review request for code stored in a Team Foundation Version Control (TFVC) repository (see Team Foundation version control (TFVC)). A code review response is created for each reviewer who provides comments.

Note

Retrieving code review comments programmatically isn't supported.

Field name Description Data type
Accepted By Name of the code reviewer.
Reference name=Microsoft.CodeReview.AcceptedBy
String
Accepted Date Date and time when the reviewer responded.
Reference name=Microsoft.CodeReview.AcceptedDate
DateTime
Associated Context Name assigned to the code change requested for review (for example, a shelveset or changeset name).
Reference name=Microsoft.CodeReview.Context
String
Associated Context Code Integer that indicates the context type: 1 = shelveset, 2 = changeset.
Reference name=Microsoft.CodeReview.ContextCode
Integer
Associated Context Owner GUID of the shelveset owner who requested the code review.
Reference name=Microsoft.CodeReview.ContextOwner
String
Associated Context Type Type of code work requested for review: Shelveset or Changeset.
Reference name=Microsoft.CodeReview.ContextType
String
Closed Status Status selected by the reviewer when closing the review. The system stores this value and writes it to the data warehouse as:

- 0—Not Reviewed
- 1—Looks Good
- 2—With Comments
- 3—Needs Work
- 4—Declined
- 5—Removed
Reference name=Microsoft.CodeReview.ClosedStatus
String
Closed Status Code Integer value (0–5) corresponding to the Closed Status selection.
Reference name=Microsoft.CodeReview.ClosedStatusCode
Integer
Closing Comments Comment entered by the reviewer when closing the review request.
Reference name=Microsoft.CodeReview.ClosingComment
String
Reviewed By Name of the team member who completed a review. The work item's state transitions to Reviewed when a reviewer responds. (Code Review Response)
Reference name=Microsoft.Common.ReviewedBy
String
Reviewed Date Date and time when the reviewer closed the request. (Code Review Response)
Reference name=Microsoft.Common.ReviewedDate
DateTime
State Code Mirror field used to track the current state value for code reviews.
Reference name=Microsoft.Common.StateCode
Integer

Fields used to track feedback

The table below lists fields that track feedback requests and responses. You complete the first three fields when you create a feedback request. The system creates one feedback response per reviewer and per item for which feedback is provided. For procedural guidance, see Get feedback.

Field name Description Data type
Application Launch Instructions Instructions that tell stakeholders how to launch the application or scenario they should review.
Reference name=Microsoft.Feedback.ApplicationLaunchInstructions
HTML
Application Start Information Guidance that orients reviewers and directs the feedback they should provide.
Reference name=Microsoft.Feedback.ApplicationStartInformation
PlainText
Application Type Type of application that reviewers evaluate. Valid values come from the ProcessConfiguration file; defaults include Web Application, Remote Machine, and Client Application.
Reference name=Microsoft.Feedback.ApplicationType
String
Rating Star-based rating that reviewers assign to an item. The system stores this value and writes it to the data warehouse as:

- 0—Not Rated
- 1—Poor
- 2—Fair
- 3—Good
- 4—Very Good
- 5—Excellent
Reference name=Microsoft.Common.Rating
String