10X: Work Tree (Team View)

About this report

The Work Tree (Team View) report provides an overview of progress on all work items in a selected program increment (PI), as well as a drill-down hierarchy of progress at each work item level, by team or teams.  Release train engineers and portfolio managers can use this report to track progress of all work items in a PI by team. Generate this report by selecting a PI and program.

Data on this report can also be shared by creating a screenshot using the Capture button on the top right of the page. This will create an image in a browser pop-up.

You can filter the Work Tree by Release Vehicle and Release Vehicle Group, Sprint, and Product by using the Configuration bar at the top of the page.

This remainder of this article focuses on the Team view.

  • Enter one or more teams in the Team multi-select field to filter the report by team. 


  1. PI must exist in the system and be tied to a program. 
  2. Epics must be created and tied to the PI.
  3. Features must be created and tied to the Epic. 
  4. Stories, with point values, must be created and tied to features.
  5. Capabilities are optional (setting must be turned on for the portfolio; will be an additional layer between epics and features), and can be tied epics. 
  6. Teams must be created, and assigned stories in the PI. 

How are report values calculated? 

Roll-up Dashboard

  1. Days Left: Days remaining, calculated between the current day and the end of the PI, not including weekends.
  2. % Story Points Accepted: Percentage of story points tied to the selected PI that are accepted.
  3. Epic Progress: A gauge showing the percentage of epics that are accepted.
  4. Feature Progress: A gauge showing the percentage of features that are accepted.
  5. Story Progress: A gauge showing the percentage of stories that are accepted; also shows the count of stories accepted from the total and the count of points completed from the total.
  6. Task Progress: A gauge showing the percentage of tasks that are accepted; also shows the count of tasks completed from the total.

Below the gauges, the hierarchy of work items is grouped by program; each program will display its own progress bar.

Program Progress Bar

The progress bar shows the percentage of story points delivered for each selected program. 

Expandable Drill-Down List/Hierarchy of Work Items

Multiple programs can be displayed in the list; expand and collapse program names as needed.

Expand each work item in the list to show child work items. For example, expand an epic in the list to see its child features--expand a feature to see a list of child stories. At the story level, click on a story to see details, including acceptance criteria and tasks.

In the Work Tree, epics are ordered by their PI ranks. All child items are ordered based on the rank under their parent and this order matches the order set in the backlog. For example, capabilities and features are ordered here as they are under an epic in the backlog, features—under an epic or a capability, and stories—under a feature.

The Orphan Stories section shows any story assigned to the PI that is not also assigned to a feature. When selecting the Orphan Stories section, the story progress meter changes and shows the overall progress of stories in the section.


  1. Work Item Name: The name of the work item; click on a work item to open it for editing; icons to the left of the name indicate the state and item type (for example, in-progress epic; hover over the icons to see its tooltip). The links icon next to a work item indicates that the item is dependent or something depends on the item. An item with predecessors has the links icon with the left arrow, an item with successors—the icon with the right arrow, and an item with both predecessors and successors—the icon with both arrows. Select the work item, and then click the View the Predecessors and Successors button on the Links tab to view the visualization chart. The chart shows the relationships between the items that have the predecessors and successors. A predecessor is a theme, an epic, a capability, a feature, or a story that comes before a certain feature. A successor is a theme, an epic, a capability, a feature, or a story that comes after a certain feature. Use the toggles on the right to highlight predecessors or successors.
  2. Health: Epic health; click the icon palette in this cell to edit the health settings. The column is displayed when the Show Health toggle found in Extra Configs is switched on.
  3. Points: Estimated points pulled from the Story Page/Story panel; the value is a roll-up of all stories tied to the work item. 
  4. Items: A count of direct child items for the work item.
  5. Progress: The percentage of story points accepted for the work item; the value is a roll-up of all points tied to the work item. 

 Note: Stand-alone features display at the same level as epics.


How to interpret this report

Roll-up Dashboard

The ideal dashboard has very little lag between story and task progress, with features not far behind. It is not unusual for epics to lag behind even further, because epics span PIs. Pay particular attention to features, to make sure they are not trailing the stories in progress; when feature progress is too far behind story progress, it indicates a prioritization problem for your stories--most likely working on stories for too many features at once. Minimizing the feature work in process allows you to finish individual features before moving on to more stories. In the Backlog, use the Rank Stories by Features option to get a baseline prioritization for stories. A Work in Process Report is also available to help you understand where a bottleneck is impacting feature progress.

Program Progress Bar

When running a report for multiple programs at once, compare the progress bars to see which programs are lagging behind in completing work items.

Expandable Drill-Down List/Hierarchy of Work Items

Review the progress of epics, features, stories, and tasks, using the drill-down function in the report, to gain insight into which work items are lagging behind or being completed on schedule. From here, you can also access the work items directly to edit if needed, such as splitting features, prioritizing work items, or reducing scope.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.