|
1 | 1 | --- |
2 | | -title: Resolve Azure Boards nest, display, and reorder issues for work items |
| 2 | +title: Resolve nest, display, and reorder issues for work items |
3 | 3 | titleSuffix: Azure Boards |
4 | | -description: Learn how to resolve error messages caused by nesting and reordering issues that occur in Azure Boards. |
| 4 | +description: Learn how to address and fix error messages caused by nesting and reordering issues that occur in Azure Boards. |
5 | 5 | ms.custom: "boards-backlogs, seodec18" |
6 | 6 | ms.service: azure-devops-boards |
7 | 7 | ms.assetid: BDEAA5D4-83A3-49FC-BEEB-EE685E92B68B |
8 | 8 | ms.topic: troubleshooting |
9 | 9 | ms.author: chcomley |
10 | 10 | author: chcomley |
11 | 11 | monikerRange: '<= azure-devops' |
12 | | -ms.date: 10/26/2021 |
| 12 | +ms.date: 07/06/2023 |
13 | 13 | --- |
14 | 14 |
|
15 | | -# Fix issues in Azure Boards with displaying, reordering, and nesting work items |
| 15 | +# Resolve nest, display, and reorder issues for work items |
16 | 16 |
|
17 | 17 | <a id="display-hierarchy"> </a> |
18 | 18 |
|
19 | 19 | [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)] |
20 | 20 |
|
21 | 21 | <!--- Supports FWLINK https://go.microsoft.com/fwlink/?linkid=529135 --> |
22 | 22 |
|
23 | | -Azure Boards backlogs display a natural hierarchy of work items. When you add parent-child links to work items not in the natural hierarchy, you'll receive a message that indicates reordering is disabled. Some items may not display. Also, the system may disable the drag-and-drop reorder feature. |
| 23 | +When you add parent-child work item links that aren't in the natural hierarchy, reordering is disabled. Items may not display and the system may disable the drag-and-drop reorder feature. |
24 | 24 |
|
25 | | -Use this article to fix the issues that occur and that display one of the following messages: |
26 | | - |
27 | | -- `You cannot reorder work items and some work items may not be shown.` |
28 | | - |
29 | | -- `You cannot reorder work items and some work items may not be shown. See work item(s) 7 to either remove the parent to child link or change the link type to 'Related'." or "Work item 3 can't be reordered because its parent is on the same category".` |
30 | | - |
31 | | -- `Items added to the backlog may disappear on a refresh because your team project marks them as "in progress". Those items appear when you change the "In progress" filter to Show.` |
| 25 | +Use this article to address error messages that are similar to the following message: |
| 26 | +- "You can't reorder work items and some work items may not be shown." |
| 27 | +- "Work item can't be reordered because its parent is on the same category." |
| 28 | +- "Items added to the backlog may disappear on a refresh because your team project marks them as "in progress." Those items appear when you change the "In progress" filter to Show." |
32 | 29 |
|
33 | 30 | > [!NOTE] |
34 | | -> This article addresses issues that arise when you create parent-child links that don't obey the natural hierarchy defined for backlogs. For other issues that may occur with multi-team ownership, see [Configure a hierarchy of teams, Exercising select features with shared area paths](../plans/configure-hierarchical-teams.md#op-issues). |
35 | | -
|
| 31 | +> For other issues that may occur with multi-team ownership, see [Configure a hierarchy of teams, Exercise select features with shared area paths](../plans/configure-hierarchical-teams.md#op-issues). |
36 | 32 |
|
37 | 33 | ## Natural hierarchy for work item types |
38 | 34 |
|
39 | | -The following image indicates the natural hierarchy for the Agile, Scrum, and Capability Maturity Model Integration (CMMI) processes. Along with these work item types, other custom work item types may be added to backlogs and boards. Also, custom backlog levels may be added. |
| 35 | +The following image shows the natural hierarchy for the Agile, Scrum, and Capability Maturity Model Integration (CMMI) processes. |
40 | 36 |
|
41 | | - |
| 37 | +:::image type="content" source="media/resolve/create-hierarchy-with-different-wits.png" alt-text="Conceptual image of natural hierarchy for the Agile, Scrum, and CMMI processes."::: |
42 | 38 |
|
43 | | -You break this natural hierarchy when you create same-category links between work items. |
| 39 | +The natural hierarchy breaks when you create same-category or same-type links between work items. For example, parent-child links that are bug-bug or user story-user story or *requirements* category-*task* category. |
44 | 40 |
|
45 | | -When you link work items of the same type with parent-child links—such as bug-bug or user story-user story—you create same-category links. Also, when you create parent-child links between work items that belong to the same category—such as the Requirements category or Task category—you create same-category links. The category a work item belongs to is determined by your process backlog levels and your team's selected bug behavior. To understand more about same-category hierarchy, see the section [Recommended configuration](#recommended). |
46 | | - |
47 | | -<a id="nested" > </a> |
| 41 | +## Recommended configuration |
48 | 42 |
|
49 | | -## Resolve the message that you can't reorder work items |
| 43 | +- Maintain a flat list, rather than nesting requirements, bugs, and tasks. Only create parent-child links one level deep between items that belong to a different category. The category a work item belongs to gets determined by your process backlog levels and your team's selected bug behavior. |
| 44 | +- Use the *feature* work item type to group user stories (Agile), issues (Basic), product backlog items (Scrum), or requirements (CMMI). You can [quickly map product backlog items to features](organize-backlog.md), which creates parent-child links in the background. |
| 45 | +- Don't create a hierarchy of backlog items, tasks, and bugs. Don't create same-category hierarchies, like parent-child links among work items of the same type, such as story-story, bug-bug, task-task, or issue-issue. The backlog, board, and sprints experiences don't support reordering for same-category hierarchies, as it introduces confusion by ordering a work item that doesn't belong on that level. |
50 | 46 |
|
51 | | -You may see a message such as `You cannot reorder work items and some work items may not be shown`. No work item IDs are listed. |
| 47 | +## Resolve - Cannot reorder work items |
52 | 48 |
|
53 | | -To address this message, take the following actions: |
| 49 | +You may see a message like: `You cannot reorder work items and some work items may not be shown`. No work item IDs are listed. |
54 | 50 |
|
55 | | -1. Open your Backlog. |
| 51 | +To address this error, do the following steps: |
56 | 52 |
|
| 53 | +1. Open your backlog. |
57 | 54 | 2. Review the list of items to determine which items of the same type are nested. |
58 | | - For example, the following shows that a user story is a child of another user story. |
| 55 | + Example #1: The following image shows a user story as a child of another user story. |
59 | 56 |
|
60 | | - > [!div class="mx-imgBorder"] |
61 | | - >  |
| 57 | + :::image type="content" source="media/resolve/nested-user-stories.png" alt-text="Screenshot of nested user stories."::: |
62 | 58 |
|
63 | | - As another example, the following shows that a bug is a child of a user story. Because the team has configured their backlog to display user stories and bugs at the same level (Requirements category), this configuration results in a nested item that disables the ordering feature. |
| 59 | + Example #2: The following image shows a bug as a child of a user story. Because the team configured their backlog to display user stories and bugs at the same level (Requirements category), this configuration results in a nested item that disables the ordering feature. |
64 | 60 |
|
65 | | - > [!div class="mx-imgBorder"] |
66 | | - >  |
| 61 | + :::image type="content" source="media/resolve/nested-user-story-bug.png" alt-text="Screenshot of nested user story and bug."::: |
67 | 62 |
|
68 | | -3. Remove all parent-child links that exist among nested items of the same work item type or same category. Or, change the link to 'Related'. |
69 | | - |
70 | | -4. Refresh your Backlog. |
| 63 | +3. Remove all parent-child links that exist among nested items of the same work item type or same category. Or, change the link to 'Related.' |
| 64 | +4. Refresh your backlog. |
71 | 65 |
|
72 | | -The issue is now resolved and the message no longer displays. |
| 66 | +The message no longer displays. |
73 | 67 |
|
| 68 | +## Resolve - Cannot reorder work items, change link type or category |
74 | 69 |
|
75 | | -## Resolve the message that specifies work item IDs |
| 70 | +You may see a message like: `You cannot reorder work items and some work items may not be shown. See work item(s) 7 to either remove the parent to child link or change the link type to 'Related'." or "Work item 3 can't be reordered because its parent is on the same category"`. |
76 | 71 |
|
77 | | -You may see a message similar to `You cannot reorder work items and some work items may not be shown. See work item(s) 7 to either remove the parent to child link or change the link type to 'Related'." or "Work item 3 can't be reordered because its parent is on the same category"`. |
78 | | - |
79 | | -To address this message, take the following action: |
| 72 | +To address this error, do the following steps: |
80 | 73 |
|
81 | 74 | 1. Open the work item listed in the error message. |
82 | | - |
83 | 75 | 2. Look for a parent or child link. Make sure this link goes to a work item within the same category as the work item you opened. This link goes to another work item that appears on the same backlog level as the work item you opened. Depending on your team's bug behavior setting, bugs may appear with requirements or tasks. |
84 | | - |
85 | 76 | 3. Remove the problem parent-child link. If you would like to keep these items associated, use 'Related' link type instead. |
86 | 77 |
|
87 | | -The issue is resolved and the message no longer displays. |
88 | | - |
89 | | -## Resolve the issue where work items that are in progress may disappear on a refresh |
| 78 | +The message no longer displays. |
90 | 79 |
|
91 | | -The message—`Items added to the backlog may disappear on a refresh because your team project marks them as "in progress". Those items appear when you change the "In progress" filter to Show.`—indicates that the **In Progress** filter for the backlog has been turned off. |
| 80 | +## Resolve - Work items in progress may disappear on refresh |
92 | 81 |
|
93 | | -Upon refresh of your browser, the backlog displays those work items based on your selected filters. |
| 82 | +You may see a message like: `Items added to the backlog may disappear on a refresh because your team project marks them as "in progress". Those items appear when you change the "In progress" filter to Show.`. This message indicates that the **In Progress** filter for the backlog is turned off. |
94 | 83 |
|
95 | | -To reset the filters, complete the following steps. |
| 84 | +When you refresh your browser, the backlog displays those work items based on your selected filters. To reset the filters, complete the following steps. |
96 | 85 |
|
97 | 86 | ::: moniker range=">= azure-devops-2019" |
| 87 | +1. Open your backlog. |
| 88 | +1. From the **View options** selector, choose to show or hide **In Progress items**. |
98 | 89 |
|
99 | | -From the **View options** selector, you can choose to show or hide **In Progress items**. If you turn the **In Progress** control off, then items that are in the *Active*, *Committed*, or *Resolved* states or states that map to the [In Progress category state](../work-items/workflow-and-state-categories.md) won't appear in the backlog. |
100 | | - |
| 90 | +- If you turn the **In Progress** control off, then items that are in the *Active*, *Committed*, or *Resolved* states or states that map to the [**In Progress** category state](../work-items/workflow-and-state-categories.md) don't appear in the backlog. |
| 91 | + |
101 | 92 | ::: moniker-end |
102 | 93 |
|
103 | | -::: moniker range=">= azure-devops-2020" |
104 | | -:::image type="content" source="media/create-backlog/in-progress-control-2020.png" alt-text="Screenshot of View options selector, In progress control, version 2020 and later."::: |
105 | | -::: moniker-end |
| 94 | +::: moniker range=">= azure-devops-2020" |
106 | 95 |
|
| 96 | + :::image type="content" source="media/create-backlog/in-progress-control-2020.png" alt-text="Screenshot of View options selector, In progress control, version 2020 and later."::: |
| 97 | + |
| 98 | +::: moniker-end |
107 | 99 | ::: moniker range="azure-devops-2019" |
108 | | -:::image type="content" source="media/create-backlog/in-progress-control-2019.png" alt-text="Screenshot of View options selector, In progress control, version 2019."::: |
| 100 | + :::image type="content" source="media/create-backlog/in-progress-control-2019.png" alt-text="Screenshot of View options selector, In progress control, version 2019."::: |
109 | 101 | ::: moniker-end |
110 | | - |
111 | 102 | ::: moniker range="tfs-2018" |
112 | | -Choose **In progress items** show or hide **In Progress** backlog items. If you turn the **In Progress items** control off, then items that are in the *Active*, *Committed*, or *Resolved* states or states that map to the [In Progress category state](../work-items/workflow-and-state-categories.md) won't appear in the backlog. |
113 | | -::: moniker-end |
| 103 | +1. Open your backlog. |
| 104 | +2. Show or hide **In progress items** on your backlog. |
| 105 | + - If you turn the **In Progress items** control off, then items that are in the *Active*, *Committed*, or *Resolved* states or states that map to the [**In Progress** category state](../work-items/workflow-and-state-categories.md) don't appear in the backlog. |
114 | 106 |
|
115 | | -You usually choose to hide **In Progress items** when you want to forecast work. For more information, see [Forecast your product backlog](../sprints/forecast.md). |
116 | | - |
117 | | - |
118 | | -<a id="recommended"> </a> |
119 | | - |
120 | | -## Recommended configuration |
121 | | - |
122 | | -While you can create a hierarchy of backlog items, tasks, and bugs—we recommend that you don't create same-category hierarchies. That is, don't create parent-child links among work items of the same type, such as story-story, bug-bug, task-task, or issue-issue. The reason is that the Backlog, Board, and Sprints experiences don't support reordering for same-category hierarchy. Since ordering is executed by hierarchy level, same-category hierarchy introduces confusion by ordering a work item that doesn't belong on that level. |
123 | | - |
124 | | -Instead of nesting requirements, bugs, and tasks, we recommend that you maintain a flat list. In other words, only create parent-child links one level deep between items that belong to a different category. |
125 | | - |
126 | | -Use the Feature work item type when you want to group user stories (Agile), issues (Basic), product backlog items (Scrum), or requirements (CMMI). You can [quickly map product backlog items to features](organize-backlog.md), which creates parent-child links in the background. |
127 | | - |
128 | | - |
129 | | -<a id="nested" > </a> |
| 107 | +::: moniker-end |
130 | 108 |
|
131 | | -<a id="bugs-as-tasks" > </a> |
| 109 | + - Hide **In Progress items** when you want to forecast work. For more information, see [Forecast your product backlog](../sprints/forecast.md). |
132 | 110 |
|
133 | 111 | ## Track bugs as requirements or tasks |
134 | 112 |
|
135 | | -As mentioned previously, [each team can choose how they want to track bugs](../../organizations/settings/show-bugs-on-backlog.md) to behave like requirements, or tasks, or as neither. |
| 113 | +[Each team can choose how to track bugs](../../organizations/settings/show-bugs-on-backlog.md), like requirements or tasks, or neither. |
136 | 114 |
|
137 | | -If you choose to track bugs as requirements, bugs should only be nested under the Feature level. |
| 115 | +If you track bugs as *requirements*, only nest bugs under the *Feature* level. |
138 | 116 |
|
139 | | -> [!div class="mx-imgBorder"] |
140 | | ->  |
| 117 | +:::image type="content" source="media/resolve/bugs-as-requirements.png" alt-text="Screenshot of linked bugs like requirements."::: |
141 | 118 |
|
142 | | -If you choose to track bugs as tasks, bugs should only be nested under the requirements level. |
| 119 | +If you track bugs as *tasks*, only nest bugs under the *Requirement* level. |
143 | 120 |
|
144 | | -> [!div class="mx-imgBorder"] |
145 | | ->  |
| 121 | +:::image type="content" source="media/resolve/bugs-as-tasks.png" alt-text="Screenshot of linked bugs like tasks."::: |
146 | 122 |
|
147 | | -<a id="leaf-nodes" > </a> |
| 123 | +## Display nested items on backlogs and boards |
148 | 124 |
|
149 | | -## How backlogs and boards display nested items |
150 | | - |
151 | | -For TFS 2018 and earlier versions, the Kanban board only shows the last node with nested items of a same-category hierarchy. For all versions, sprint backlogs and Taskboards only show the last node in a same-category hierarchy, called the leaf node. |
| 125 | +Sprint backlogs and Taskboards only show the last node in a same-category hierarchy, called the leaf node. |
152 | 126 |
|
153 | 127 | ::: moniker range="tfs-2018" |
154 | | - |
155 | 128 | > [!NOTE] |
156 | | -> For TFS 2018.2 and later versions, Kanban boards display all work items of nested same-category work items. |
157 | | -
|
| 129 | +> - For TFS 2018 and earlier versions, the Kanban board only shows the last node with nested items of a same-category hierarchy. |
| 130 | +> - For TFS 2018.2 and later versions, Kanban boards display all work items of nested same-category work items. |
158 | 131 | ::: moniker-end |
159 | 132 |
|
160 | 133 | ::: moniker range="tfs-2018" |
161 | 134 |
|
162 | 135 | ### Product backlog and Kanban boards |
163 | 136 |
|
164 | | -For example, if you link items within a same-category hierarchy that is four levels deep, only the items at the fourth level appear on the Kanban board, sprint backlog, and taskboard. |
| 137 | +If you link items within a same-category hierarchy that is four levels deep, for example, only the items at the fourth level appear on the Kanban board, sprint backlog, and Taskboard. |
165 | 138 |
|
166 | 139 | As shown in the following images, the third user story, *Interim save on long form*, has a child bug, *Save takes too long*. The child bug, *Save takes too long*, appears on the Kanban board, but not the parent user story. |
167 | 140 |
|
168 | 141 | **All bugs and requirements appear on the backlog** |
169 | 142 |
|
170 | | - |
| 143 | +:::image type="content" source="media/resolve/bugs-appear-on-backlog.png" alt-text="Screenshot showing child bug on backlog."::: |
171 | 144 |
|
172 | 145 | **Only leaf nodes appear on the Kanban board** |
173 | 146 |
|
174 | | - |
| 147 | +:::image type="content" source="media/resolve/bugs-appear-on-board.png" alt-text="Screenshot showing leaf node bug on Kanban board."::: |
175 | 148 |
|
176 | 149 | ::: moniker-end |
177 | 150 |
|
178 | | -<a id="bugs-as-tasks" > </a> |
179 | | - |
180 | 151 | ### Sprint backlogs and Taskboards |
181 | 152 |
|
182 | | -When bugs appear in the backlog with tasks, linking tasks and bugs to their parent requirements groups them correctly on the sprint backlog and taskboard. |
183 | | -But, if you create parent-child links between a requirement and a bug, and the bug and a task, as shown here, the task appears on the sprint backlog and taskboard, but not the bug. |
| 153 | +When bugs appear in the backlog with tasks, linking tasks and bugs to their parent requirements groups them correctly on the sprint backlog and Taskboard. |
| 154 | +But, if you create parent-child links between a requirement and a bug, and the bug and a task, as shown here, the task appears on the sprint backlog and Taskboard, but not the bug. |
184 | 155 |
|
185 | 156 | **Hierarchy of items assigned to a sprint backlog** |
186 | 157 |
|
187 | | - |
| 158 | +:::image type="content" source="media/resolve/sprint-backlog-hierarchy.png" alt-text="Screenshot of Sprint backlog query with linked bug and task."::: |
188 | 159 |
|
189 | 160 | **Only leaf nodes appear on sprint backlogs** |
190 | 161 |
|
191 | | - |
| 162 | +:::image type="content" source="media/resolve/sprint-backlog-leaf-only.png" alt-text="Screenshot of Sprint backlog with leaf node task."::: |
192 | 163 |
|
193 | | -**Only leaf nodes appear on Taskboards** |
194 | | - |
195 | | -Is there a workaround to display intermediate nodes within a hierarchy? Not at this time. You can always check the entire list of items assigned to a sprint by using the **Create Query** link. |
| 164 | +**Only leaf nodes appear on Taskboards** |
196 | 165 |
|
| 166 | +:::image type="content" source="media/resolve/bugs-appear-on-taskboard.png" alt-text="Screenshot of Sprint board with leaf node task."::: |
| 167 | + |
| 168 | +## Q: Is there a workaround to display intermediate nodes within a hierarchy? |
| 169 | +A: No, not at this time. You can always check the entire list of items assigned to a sprint when you select **Create query**. |
197 | 170 |
|
198 | 171 | ## Related articles |
199 | 172 |
|
200 | | -- [Set up your Backlogs and Boards](set-up-your-backlog.md) |
201 | | -- [About Boards and Kanban, Limitations of multi-team Kanban board views](../boards/kanban-overview.md#limits-multi-team) |
202 | | - |
| 173 | +- [Set up your backlogs and boards](set-up-your-backlog.md) |
| 174 | +- [About boards and Kanban, Limitations of multi-team Kanban board views](../boards/kanban-overview.md#limits-multi-team) |
| 175 | + |
0 commit comments