|
1 | 1 | --- |
2 | 2 | title: Code review and feedback field reference |
3 | 3 | titleSuffix: Azure Boards |
4 | | -description: Learn how to use the code review and feedback fields to track code review and feedback requests and responses for Azure Boards and Azure DevOps. |
| 4 | +description: Learn how to use the code review and feedback fields to track code review and feedback requests and responses. |
5 | 5 | ms.service: azure-devops-boards |
6 | 6 | ms.assetid: 4182c1c5-a768-4f4d-b6cb-862fc57e6ab4 |
7 | 7 | ms.topic: conceptual |
8 | 8 | ms.author: chcomley |
9 | 9 | author: chcomley |
10 | 10 | monikerRange: '<= azure-devops' |
11 | | -ms.date: 11/07/2021 |
| 11 | +ms.date: 05/12/2025 |
12 | 12 | --- |
13 | 13 |
|
14 | | -# Code review and feedback field reference in Azure Boards and Azure DevOps |
| 14 | +# Code review and feedback field reference |
15 | 15 |
|
16 | 16 | [!INCLUDE [version-lt-eq-azure-devops](../../../includes/version-lt-eq-azure-devops.md)] |
17 | 17 |
|
18 | | -You can use the code review and feedback fields to create queries and reports that track the status of these processes. The fields appear in the following work item types, which are included with the default processes for Azure Boards and TFS: Code Review Request, Code Review Response, Feedback Request, and Feedback Response. |
19 | | - |
| 18 | +This article provides a detailed reference for the fields used to track code reviews and feedback, including their descriptions, data types, and usage. It also explains how you can use these fields to monitor and manage code review and feedback workflows effectively. |
20 | 19 |
|
| 20 | +Use the code review and feedback fields to create queries and reports that track the status of these processes. These fields are available for default work item types: Code Review Request, Code Review Response, Feedback Request, and Feedback Response. |
21 | 21 |
|
22 | 22 | <a name="codereviews"></a> |
23 | 23 | <a id="fields"></a> |
24 | 24 |
|
25 | 25 | ## Fields used to track code reviews |
26 | 26 |
|
27 | | - The following fields are used to track code review requests and responses. You can only make a Code Review request against code maintained in a [Team Foundation version control (TFVC) repository](../../../repos/tfvc/index.yml). A code review response is created for each person who provides review comments. See [Day in the life of a Developer: Suspend work, fix a bug, and conduct a code review](../../../repos/tfvc/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review.md). |
| 27 | +The following fields are used to track code review requests and responses. You can only make a Code Review request against code maintained in a [Team Foundation version control (TFVC) repository](../../../repos/tfvc/index.yml). A code review response is created for each person who provides review comments. See [Day in the life of a Developer: Suspend work, fix a bug, and conduct a code review](../../../repos/tfvc/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review.md). |
28 | 28 |
|
29 | 29 | > [!NOTE] |
30 | 30 | > Retrieving code review comments programmatically isn't a supported feature. |
31 | 31 |
|
32 | | - |
33 | | -> [!div class="mx-tdCol2BreakAll"] |
34 | | -> |**Field name**|**Description**|**Data type**| |
35 | | -> |--------------|---------------|-------------| |
36 | | -> |**Accepted By**|The name of the code reviewer.<br/>Reference name=Microsoft.VSTS.CodeReview.AcceptedBy|String| |
37 | | -> |**Accepted Date**|The date and time when the code-reviewer responded.<br/>Reference name=Microsoft.VSTS.CodeReview.AcceptedDate|DateTime| |
38 | | -> |**Associated Context**|The name assigned to the code work requested for review.<br/>Reference name=Microsoft.VSTS.CodeReview.Context|String| |
39 | | -> |**Associated Context Code**|An integer value that captures whether the code review is for **1** (shelveset) or **2** (changeset).<br/>Reference name=Microsoft.VSTS.CodeReview.ContextCode|Integer| |
40 | | -> |**Associated Context Owner**|The GUID assigned to the shelveset owner who requested the code review.<br/>Reference name=Microsoft.VSTS.CodeReview.ContextOwner|String| |
41 | | -> |**Associated Context Type**|The type of code work requested for review: **Shelveset** or **Changeset**.<br/>Reference name=Microsoft.VSTS.CodeReview.ContextType|String| |
42 | | -> |**Closed Status**|The status selected by the reviewer when closing the code review request. The number is stored in the system and written to the data warehouse as follows:<br/><br/>- **0 — Not Reviewed**<br />- **1 - Looks Good**<br />- **2 - With Comments**<br/>- **3- Needs Work**<br />- **4 - Declined**<br/>- **5 - Removed**<br/>Reference name=Microsoft.VSTS.CodeReview.ClosedStatus|String| |
43 | | -> |**Closed Status Code**|A value ranging from 0 to 5 that corresponds to the status selected by the reviewer when closing the code review request.<br/>Reference name=Microsoft.VSTS.CodeReview.ClosedStatusCode|Integer| |
44 | | -> |**Closing Comments**|The comment entered by the reviewer when closing the review request.<br/>Reference name=Microsoft.VSTS.CodeReview.ClosingComment|String| |
45 | | -> |**Reviewed By**|The name of the team member who reviewed the code. The State transitions to Reviewed when the code reviewer responds. (Code Review Response)<br/>Reference name=Microsoft.VSTS.Common.ReviewedBy|String| |
46 | | -> |**Reviewed Date**|The date-time stamp when the reviewer closed the request. (Code Review Response)<br/>Reference name=Microsoft.VSTS.Common.ReviewedDate|Date-Time| |
47 | | -> |**State Code**|Mirror field used to track the current state in code.<br/>Reference name=Microsoft.VSTS.Common.StateCode|Integer| |
| 32 | +|**Field name**|**Description**|**Data type**| |
| 33 | +|--------------|---------------|-------------| |
| 34 | +|**Accepted By**|The name of the code reviewer.<br/>Reference name=`Microsoft.CodeReview.AcceptedBy`|String| |
| 35 | +|**Accepted Date**|The date and time when the code-reviewer responded.<br/>Reference name=`Microsoft.CodeReview.AcceptedDate`|DateTime| |
| 36 | +|**Associated Context**|The name assigned to the code work requested for review.<br/>Reference name=`Microsoft.CodeReview.Context`|String| |
| 37 | +|**Associated Context Code**|An integer value that captures whether the code review is for **1** (shelveset) or **2** (changeset).<br/>Reference name=`Microsoft.CodeReview.ContextCode`|Integer| |
| 38 | +|**Associated Context Owner**|The GUID assigned to the shelveset owner who requested the code review.<br/>Reference name=`Microsoft.CodeReview.ContextOwner`|String| |
| 39 | +|**Associated Context Type**|The type of code work requested for review: **Shelveset** or **Changeset**.<br/>Reference name=`Microsoft.CodeReview.ContextType`|String| |
| 40 | +|**Closed Status**|The status selected by the reviewer when closing the code review request. The number is stored in the system and written to the data warehouse as follows:<br/><br/>- **0—Not Reviewed**<br />- **1 - Looks Good**<br />- **2 - With Comments**<br/>- **3- Needs Work**<br />- **4 - Declined**<br/>- **5 - Removed**<br/>Reference name=`Microsoft.CodeReview.ClosedStatus`|String| |
| 41 | +|**Closed Status Code**|A value ranging from 0 to 5 that corresponds to the status selected by the reviewer when closing the code review request.<br/>Reference name=`Microsoft.CodeReview.ClosedStatusCode`|Integer| |
| 42 | +|**Closing Comments**|The comment entered by the reviewer when closing the review request.<br/>Reference name=`Microsoft.CodeReview.ClosingComment`|String| |
| 43 | +|**Reviewed By**|The name of the team member who reviewed the code. The State transitions to Reviewed when the code reviewer responds. (Code Review Response)<br/>Reference name=`Microsoft.Common.ReviewedBy`|String| |
| 44 | +|**Reviewed Date**|The date-time stamp when the reviewer closed the request. (Code Review Response)<br/>Reference name=`Microsoft.Common.ReviewedDate`|Date-Time| |
| 45 | +|**State Code**|Mirror field used to track the current state in code.<br/>Reference name=`Microsoft.Common.StateCode`|Integer| |
48 | 46 |
|
49 | 47 | <a name="feedback"></a> |
50 | 48 |
|
51 | 49 | ## Fields used to track feedback |
52 | 50 |
|
53 | | - The following fields track feedback requests and responses. You complete the first three fields in the feedback request form. A feedback response is created for each person and for each item for which feedback is provided. See [Get feedback](/previous-versions/azure/devops/project/feedback/get-feedback). |
| 51 | +The following fields track feedback requests and responses. You complete the first three fields in the feedback request form. A feedback response is created for each person and for each item for which feedback is provided. See [Get feedback](/previous-versions/azure/devops/project/feedback/get-feedback). |
54 | 52 |
|
55 | 53 | |**Field name**|**Description**|**Data type**| |
56 | 54 | |--------------------|---------------------|-------------------| |
57 | | -|**Application Launch Instructions**|Instructions to stakeholders on how to start the application.<br/>Reference name=Microsoft.VSTS.Feedback.ApplicationLaunchInstructions|HTML| |
58 | | -|**Application Start Information**|Guidelines to direct stakeholder feedback.<br/>Reference name=Microsoft.VSTS.Feedback.ApplicationStartInformation|PlainText| |
59 | | -|**Application Type**|The type of application that stakeholders provide feedback on. The valid types are specified in the process configuration file, ProcessConfiguration. The default values are **Web Application**, **Remote Machine**, and **Client Application**.<br/>Reference name=Microsoft.VSTS.Feedback.ApplicationType|String| |
60 | | -|**Rating**|The number of stars that an item receives from a reviewer in a star-based ranking system. (Feedback Response)<br /> The number is stored in the system and written to the data warehouse as follows:<br /><br /> - **0 — Not Rated**<br />- **1 - Poor**<br />- **2 - Fair**<br />- **3- Good**<br />- **4- Very Good**<br />- **5 - Excellent**<br/>Reference name=Microsoft.VSTS.Common.Rating|String| |
| 55 | +|**Application Launch Instructions**|Instructions to stakeholders on how to start the application.<br/>Reference name=`Microsoft.Feedback.ApplicationLaunchInstructions`|HTML| |
| 56 | +|**Application Start Information**|Guidelines to direct stakeholder feedback.<br/>Reference name=`Microsoft.Feedback.ApplicationStartInformation`|PlainText| |
| 57 | +|**Application Type**|The type of application that stakeholders provide feedback on. The valid types are specified in the process configuration file, ProcessConfiguration. The default values are **Web Application**, **Remote Machine**, and **Client Application**.<br/>Reference name=`Microsoft.Feedback.ApplicationType`|String| |
| 58 | +|**Rating**|The number of stars that an item receives from a reviewer in a star-based ranking system. (Feedback Response)<br /> The number is stored in the system and written to the data warehouse as follows:<br /><br /> - **0—Not Rated**<br />- **1 - Poor**<br />- **2 - Fair**<br />- **3- Good**<br />- **4- Very Good**<br />- **5 - Excellent**<br/>Reference name=`Microsoft.Common.Rating`|String| |
61 | 59 |
|
62 | 60 | ## Related articles |
63 | 61 |
|
64 | | -- [Index of work item fields](work-item-field.md) |
65 | | -- [Get feedback](/previous-versions/azure/devops/project/feedback/get-feedback) |
66 | | -- [Day in the life of a Developer: Suspend work, fix a bug, and conduct a code review](../../../repos/tfvc/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review.md) |
| 62 | +- [Explore the index of work item fields](work-item-field.md) |
| 63 | +- [Provide and gather feedback](/previous-versions/azure/devops/project/feedback/get-feedback) |
| 64 | +- [Suspend work, fix a bug, and conduct a code review](../../../repos/tfvc/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review.md) |
0 commit comments