You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/boards/includes/common-work-item-fields.md
+17-22Lines changed: 17 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,24 +2,23 @@
2
2
ms.topic: include
3
3
ms.author: chcomley
4
4
author: chcomley
5
-
ms.date: 06/07/2023
5
+
ms.date: 07/30/2025
6
6
---
7
7
8
-
9
8
## Definitions for common work tracking fields
10
9
11
10
<aid="definitions-in-common"></a>
12
11
13
-
The following fields and tabs appear in most work items. Each tab gets used to track specific information, such as :::image type="icon" source="../backlogs/media/icon-history-tab-wi.png" border="false"::: **History**, :::image type="icon" source="../backlogs/media/icon-links-tab-wi.png" border="false"::: **Links**, or :::image type="icon" source="../backlogs/media/icon-attachments-tab-wi.png" border="false"::: **Attachments**. These three tabs provide a history of changes, view of linked work items, and ability to view and attach files.
12
+
The following fields and tabs appear in most work items. Each tab is used to track specific information. Commonly used tabs include :::image type="icon" source="../backlogs/media/icon-history-tab-wi.png"::: **History**, :::image type="icon" source="../backlogs/media/icon-links-tab-wi.png"::: **Links**, and :::image type="icon" source="../backlogs/media/icon-attachments-tab-wi.png"::: **Attachments**.
14
13
15
-
The only required field for all work item types is **Title**. When you save a work item, the system assigns it a unique **ID**. The form highlights required field in yellow. For information about other fields, see [Work item field index](../work-items/guidance/work-item-field.md).
14
+
The only required field for all work item types is **Title**. When you save a work item, the system assigns a unique identifier, **ID**. The form highlights required fields in yellow. For information about other fields, see [Work item field index](../work-items/guidance/work-item-field.md).
16
15
17
16
> [!NOTE]
18
-
> Additional fields may be required depending on customizations made to your process and project.
17
+
> Other fields might be required depending on customizations made to your process and project.
19
18
20
19
:::row:::
21
20
:::column span="1":::
22
-
**Field/tab**
21
+
**Field or Tab**
23
22
:::column-end:::
24
23
:::column span="3":::
25
24
**Usage**
@@ -31,74 +30,70 @@ The only required field for all work item types is **Title**. When you save a wo
31
30
[Title](../queries/titles-ids-descriptions.md)
32
31
:::column-end:::
33
32
:::column span="3":::
34
-
Enter a description of 255 characters or less. You can always modify the title later.
33
+
Enter a description of 255 characters or less. You can modify the **Title** later.
Assign the work item to the team member responsible for performing the work.
41
+
Assign the work item to the team member responsible for performing the work, or leave blank and complete the assignment later.
43
42
:::column-end:::
44
43
:::row-end:::
45
44
:::row:::
46
45
:::column span="1":::
47
46
[State](../queries/query-by-workflow-changes.md)
48
47
:::column-end:::
49
48
:::column span="3":::
50
-
When the work item is created, the State defaults to the first state in the workflow. As work progresses, update it to reflect the current state.
49
+
When you first create a work item, the **State** field automatically shows the first state in the workflow, such as **New** or **Unassigned**. As work progresses, update the **State**to reflect the current status of the work item.
51
50
:::column-end:::
52
51
:::row-end:::
53
52
:::row:::
54
53
:::column span="1":::
55
54
[Reason](../queries/query-by-workflow-changes.md)
56
55
:::column-end:::
57
56
:::column span="3":::
58
-
Use the default first. Update it when you change state. Each Stateis associated with a default reason.
57
+
When you first create a work item, set the default **Reason** value, such as **Created** or **New work item**. As the **State** changes for the work item, update the **Reason** value accordingly. Each **State** for the work item is associated with a default **Reason** value.
Choose the area path associated with the product or team, or leave blank until assigned during a planning meeting. To change the dropdown list of areas, see [Define area paths and assign to a team](../../organizations/settings/set-area-paths.md).
65
+
Choose the area path associated with the product or team, or leave blank and enter an appropriate value later. You can change the dropdown list of available areas. For more information, see [Define area paths and assign to a team](../../organizations/settings/set-area-paths.md).
Choose the sprint or iteration in which the work is to be completed, or leave it blank and assign it later, during a planning meeting. To change the drop-down list of iterations, see [Define iteration paths (sprints) and configure team iterations](../../organizations/settings//set-iteration-paths-sprints.md).
73
+
Choose the sprint or iteration in which to complete the work item, or leave blank and assign the value later. You can change the dropdown list of iterations. For more information, see [Define iteration paths (sprints) and configure team iterations](../../organizations/settings//set-iteration-paths-sprints.md).
Review the audit trail that the system captures and capture additional information.
83
-
84
-
Every time that the work item is updated, information is appended to the history. History includes the date of the change, who made the change, and which fields were changed. You can also add formatted text to the history field.
81
+
View the work item **History** to see all changes made to the item, as captured by the system. Each time a work item is updated, the details are appended to the history. You see the change date, the change author, and the list of updated fields. You can also add formatted text to the **History** field.
Add all types of links, such as hyperlinks, changesets, source files, and so on.
93
-
94
-
This tab also lists all links defined for the work item.
89
+
Add **Links** to create connections with other work items. Many kinds of links are supported, such as hyperlinks, changesets, source files, and more. Specify the relationship of the linked item to the work item, such as _Parent_, _Found in Build_, or _Test Result_.
Share more detailed information by adding files to the work item, such as email threads, documents, images, log files, or other file types.
97
+
Use **Attachments** to include supporting information about the work item with the item. Attach email threads, documents, images, log files, or other file types.
Copy file name to clipboardExpand all lines: docs/boards/includes/discussion-tip-azure-devops.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ ms.service: azure-devops-boards
3
3
ms.author: chcomley
4
4
author: chcomley
5
5
ms.topic: include
6
-
ms.date: 10/08/2024
6
+
ms.date: 07/30/2025
7
7
---
8
8
9
9
## Capture comments in the Discussion section
@@ -14,30 +14,32 @@ Use the **Discussion** section to add and review comments made about the work be
14
14
15
15
The rich text editor toolbar appears under the text entry area when you place your cursor in any text box that supports text formatting.
16
16
17
-
:::image type="content" source="../queries/media/share-plans/discussion-rich-text-editor-toolbar.png" alt-text="Screenshot of Discussion section, New Rich Text Editor toolbar.":::
17
+
:::image type="content" source="../queries/media/share-plans/discussion-rich-text-editor-toolbar.png" alt-text="Screenshot of Discussion section, Rich Text Editor toolbar.":::
18
18
19
19
> [!NOTE]
20
20
> A Discussion work item field doesn't exist. To query work items with comments from the Discussion area, filter on the [History field](../queries/history-and-auditing.md). The full content of the text entered in the Discussion text box is added to the History field.
21
21
22
22
### Mention someone, a group, work item, or pull request
23
23
24
-
Select one of the following icons to open a menu of recent entries where you mentioned someone, linked to a work item, or linked to a pull request. Alternatively, you can open the same menu by entering `@`, `#`, or `!`.
24
+
Select one of the following icons to open a menu of recent entries where you mentioned someone, linked to a work item, or linked to a pull request:
You can open the same menu by using keyboard shortcuts: at-mention **@**, hash tag **#**, and exclamation point **!**.
29
31
30
32
:::image type="content" source="../media/discussion-at-mention.png" alt-text="Screenshot of Discussion section, at-mention drop-down menu people-picker.":::
31
33
32
-
Enter a name or number to filter the menu list to match your entry. Select the entry you want to add. To bring a group into the discussion, enter `@` followed by the group name, such as a team or security group.
34
+
Enter a name or number to filter the menu list to match your entry. Select the entry you want to add. To bring a group into the discussion, enter the **at** symbol **@** followed by the group name, such as a team or security group.
33
35
34
36
### Edit or delete a comment
35
37
36
-
To edit or delete any of your discussion comments, choose :::image type="icon" source="../../media/icons/edit.png" border="false"::: **Edit**or choose the :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon and then choose**Delete**.
38
+
To edit or delete any of your discussion comments, select **Edit**:::image type="icon" source="../../media/icons/edit.png"::: or **More actions**(:::image type="icon" source="../../media/icons/actions-icon.png":::) and then select**Delete**:
37
39
38
40
:::image type="content" source="../media/discussion-edit-delete.png" alt-text="Screenshot of Discussion section where you can choose Edit or Delete actions.":::
39
41
40
-
After you update the comment, select **Update**. To delete the comment, confirm that you want to delete it. The **History** tab on the work item form maintains a full audit trail of all edited and deleted comments.
42
+
After you update the comment, select **Update**. To delete the comment, confirm the deletion. The **History** tab on the work item form maintains a full audit trail of all edited and deleted comments.
41
43
42
44
::: moniker range="< azure-devops"
43
45
@@ -50,7 +52,7 @@ After you update the comment, select **Update**. To delete the comment, confirm
50
52
51
53
### Add a reaction to a comment
52
54
53
-
Add one or more reactions to a comment by choosing a smiley icon at the upper-right corner of any comment. Choose from the icons at the bottom of a comment next to any existing reactions. To remove your reaction, choose the reaction on the bottom of your comment. The following image shows an example of the experience of adding a reaction, and the display of reactions on a comment.
55
+
Add one or more reactions to a comment by choosing an emoji icon at the top right of any comment. Choose from the icons at the bottom of a comment next to any existing reactions. To remove your reaction, choose the reaction on the bottom of your comment. The following image shows an example of the experience of adding a reaction, and the display of reactions on a comment.
54
56
55
57
:::image type="content" source="../media/discussion-comments-reactions.png" alt-text="Screenshot of Discussion section, add a reaction to a comment.":::
56
58
@@ -62,13 +64,13 @@ Add one or more reactions to a comment by choosing a smiley icon at the upper-ri
If you only have permissions to add to the **Discussion** of a work item, then you can do so by saving comments. This permission is controlled by Area Path nodes and the **Edit work item comments in this node** permission. For more information, see [Set work tracking permissions, Create child nodes, modify work items under an area or iteration path](../../organizations/security/set-permissions-access-work-tracking.md#set-permissions-area-path).
67
+
If you only have permissions to add to the **Discussion** of a work item, then you can do so by saving comments. This permission is controlled by Area Path nodes and the **Edit work item comments in this node** permission. For more information, see [Set work tracking permissions - Create child nodes, modify work items under an area or iteration path](../../organizations/security/set-permissions-access-work-tracking.md#set-permissions-area-path).
66
68
67
69
When you save the comments, you don't need to save the work item.
68
70
69
71
:::image type="content" source="../work-items/media/view-add/save-comments-discussion-control.png" alt-text="Screenshot of Discussion section, save comment.":::
70
72
71
73
> [!NOTE]
72
-
> When you save changes made to the **Discussion** control, only the comment gets saved. No [work item rules](../../organizations/settings/work/rule-reference.md) defined for the work item type are executed.
74
+
> When you save changes made to the **Discussion** control, only the comment is saved. No [work item rules](../../organizations/settings/work/rule-reference.md) defined for the work item type are executed.
0 commit comments