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/backlogs/display-rollup.md
+20-17Lines changed: 20 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,34 +1,37 @@
1
1
---
2
2
title: Display rollup columns to show progress, counts, or totals in Azure Boards
3
3
titleSuffix: Azure Boards
4
-
description: Learn how to add or remove the rollup column displays that show progress or totals of hierarchical items in Azure Boards.
4
+
description: Learn how to add rollup columns that automatically sum child work item values to display progress bars, counts, and totals on parent items in Azure Boards.
5
5
ms.service: azure-devops-boards
6
6
ms.topic: how-to
7
7
ms.author: chcomley
8
8
author: chcomley
9
9
ai-usage: ai-assisted
10
-
monikerRange: '>= azure-devops-2020'
11
-
ms.date: 09/16/2024
10
+
monikerRange: '<= azure-devops'
11
+
ms.date: 07/01/2025
12
+
# customer intent: As a team member, I want to display rollup columns that automatically sum child work item values so that I can track progress, counts, and totals across my backlog hierarchy.
12
13
---
13
14
14
15
# Display rollup progress or totals in Azure Boards
This article provides an overview of rollup functionality in Azure DevOps, explaining how rollup sums values of select fields for all child work items of a parent. Rollup is commonly used for estimated or completed work, effort, size, or story points. However, rollup of Effort, Story Points, or Size fields across product and portfolio backlogs isn't supported. This article also guides you through the steps to implement rollup functionality in various contexts such as product and portfolio backlogs, sprint Planning pane, sprint backlogs, and taskboards.
19
-
20
-
In the following example, **Progress by Work Items** displays progress bars for parent work items based on the percentage of closed descendant items. For Epics, descendant items include all child Features and their child or grandchild work items. For Features, descendant items include all child User Stories and their child work items.
19
+
Rollup automatically sums child work item values to display totals on parent items. Use it to track work estimates, effort, size, or story points across your backlog hierarchy. Learn how to add rollup columns to backlogs, sprint planning, and taskboards.
21
20
22
21
> [!IMPORTANT]
23
-
> - Rollup data supports progress bars, counts of work items, and sums of numeric fields within a project. Child items linked to a different project aren't included in the parent rollup calculations.
24
-
> - Links to test cases or test artifacts aren't included in rollup calculations, as these items are linked using test-specific link types.
22
+
> - Rollup supports progress bars, work item counts, and numeric field sums within a project only
23
+
> - Cross-project child items and test case links aren't included in rollup calculations
24
+
> - Rollup of Effort, Story Points, or Size fields isn't supported across product and portfolio backlogs
25
+
26
+
In the following example, **Progress by Work Items** shows progress bars based on the percentage of closed descendant items. For Epics, this includes all child Features and their descendants. For Features, this includes all child User Stories and their descendants.
27
+
25
28
> [!div class="mx-imgBorder"]
26
29
> 
27
30
28
31
::: moniker range="azure-devops"
29
32
30
33
> [!NOTE]
31
-
> You can view rollup progress in the new version of Delivery Plans, now available in public preview for Azure Boards. This feature is integrated into Azure Boards and is no longer an extension. To enable it, see [Manage or enable features](../../project/navigation/preview-features.md) and turn on **New Delivery Plans Experience**. For more information, see [Review team Delivery Plans](../plans/review-team-plans.md).
34
+
> Rollup progress is available in the new Delivery Plans (public preview). Enable **New Delivery Plans Experience** in [preview features](../../project/navigation/preview-features.md). For more information, see [Review team Delivery Plans](../plans/review-team-plans.md).
32
35
33
36
::: moniker-end
34
37
@@ -97,15 +100,16 @@ Each user can customize their column options, and these settings persist across
97
100
98
101
Open a portfolio backlog and select **In Progress Items** and **Completed Child Items**. This allows you to compare the State value of items with the rollup value.
2. Select **Column options**, or select the :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon and then select **Column options**.
103
107
104
108
> [!div class="mx-imgBorder"]
105
109
> 
106
110
107
111
> [!TIP]
108
-
> The Column options you select apply to the chosen backlog level and will persist across your sessions until you change them.
112
+
> The Column options you select apply to the chosen backlog level and persists across your sessions until you change them.
109
113
110
114
## Add a rollup column
111
115
@@ -114,8 +118,7 @@ Each user can customize their column options, and these settings persist across
114
118
> [!div class="mx-imgBorder"]
115
119
> 
116
120
117
-
> [!NOTE]
118
-
> The menu options vary based on the process chosen for your project, the selected backlog level, and whether the **Show parents** view option is enabled.
121
+
The menu options vary based on the process chosen for your project, the selected backlog level, and whether the **Show parents** view option is enabled.
119
122
120
123
For example, the following image shows that the Count of Tasks for the parent user stories is 2 and 4, respectively. The Count of Tasks for the parent Feature and Epic is 6.
121
124
@@ -167,14 +170,14 @@ Use the following methods to get rollup data:
167
170
168
171
## Analytics, latency, and error states
169
172
170
-
Rollup data gets calculated from the Analytics service. When dealing with a large amount of data, you might experience some latency in displaying rollup. Hover over the :::image type="icon" source="../../media/icons/rollup.png" border="false"::: rollup icon to determine the state of the data.
173
+
Rollup data is calculated from the Analytics service. Large datasets may cause display latency. Hover over the :::image type="icon" source="../../media/icons/rollup.png" border="false"::: rollup icon to check data status.
171
174
172
-
If an error occurs in retrieving rollup data, you see an :::image type="icon" source="../../media/icons/info.png" border="false"::: info icon and empty rows. Errors indicate when the Analytics data was last updated, meaning the Analytics services are still processing changes that might affect rollup calculations. Once the Analytics data is up to date, the rollup columns refresh with the latest data.
175
+
Errors appear as an :::image type="icon" source="../../media/icons/info.png" border="false"::: info icon with empty rows, indicating the Analytics service is still processing recent changes. Rollup columns refresh automatically once processing completes.
Copy file name to clipboardExpand all lines: docs/boards/backlogs/filter-backlogs-boards-plans.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Filter functions are available from all Azure Boards tools: Work items, Boards,
54
54
55
55
The following table indicates the supported options based on the tool indicated with a ✔️ or is listed.
56
56
57
-
Backlogs and boards are subject to filters defined for the team as described in [Set up your Backlogs and Boards](set-up-your-backlog.md). Other tools have predefined filters based on the view, query filter clauses, or settings you select.
57
+
Backlogs and boards are subject to filters defined for the team as described in [Create and manage your backlog](create-your-backlog.md). Other tools have predefined filters based on the view, query filter clauses, or settings you select.
58
58
59
59
:::row:::
60
60
:::column span="1.5":::
@@ -507,7 +507,7 @@ Along with the standard filter functions summarized in the previous table, the f
507
507
508
508
509
509
**Notes**
510
-
1. The **Work items** page is subject to filters based on the [view selected](../work-items/view-add-work-items.md#view-work-items). **Boards** and **Backlogs** are subject to filters defined for the team as described in [Set up your Backlogs and Boards](set-up-your-backlog.md). Completed and In Progress work items get determined based on the state categories assigned to the workflow state as described in [How workflow states and state categories are used in Backlogs and Boards](../work-items/workflow-and-state-categories.md#category-states).
510
+
1. The **Work items** page is subject to filters based on the [view selected](../work-items/view-add-work-items.md#view-work-items). **Boards** and **Backlogs** are subject to filters defined for the team. Completed and In Progress work items get determined based on the state categories assigned to the workflow state as described in [How workflow states and state categories are used in Backlogs and Boards](../work-items/workflow-and-state-categories.md#category-states).
511
511
2. Grouping is supported through portfolio backlogs and boards, parent-child links, and tree hierarchy. Tree hierarchies are flattened when filtering is applied and reinstated when filtering is cleared.
512
512
3.**Backlogs** and **Sprint Backlogs** support reordering. However, when filtering is enabled, reordering isn't supported.
513
513
4.**Taskboards** provides a **Group by** function based on **People** or **Stories**.
@@ -753,7 +753,7 @@ For more information, see [Query work item history and discussion fields](../que
753
753
754
754
## Related articles
755
755
756
-
-[Set up your Backlogs and Boards](set-up-your-backlog.md)
756
+
-[Create and manage you backlog](create-your-backlog.md)
Copy file name to clipboardExpand all lines: docs/boards/backlogs/manage-issues-impediments.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ Define tasks when you want to create a [checklist of tasks](../boards/add-task-c
64
64
::: moniker range="<azure-devops"
65
65
66
66
> [!NOTE]
67
-
> If your project collection uses the On-premises XML process model to customize work tracking, you can enable work item types that you add to the Task Category to appear as a checklist on your product board. To learn how, see [Set up your backlogs and boards, Customize your board checklist items](set-up-your-backlog.md#customize-checklist-2019).
67
+
> If your project collection uses the On-premises XML process model to customize work tracking, you can enable work item types that you add to the Task Category to appear as a checklist on your product board.
0 commit comments