---
title: "Breakdown"
canonical: "https://wiki.brokenbuild.net/space/WIP/4527423578/Breakdown"
format: markdown
---
### Applies to

> ℹ️ - [WIP Aging chart](https://brokenbuild.atlassian.net/wiki/spaces/WIP/pages/4493279256)
> ℹ️ - [WIP Run chart](https://brokenbuild.atlassian.net/wiki/spaces/WIP/pages/4798709796)

### Navigation

> ℹ️ **Below the chart**

When analyzing delivery data, it’s important to segment it by meaningful issue fields to gain deeper insights into trends and anomalies. The Breakdown feature allows you to do this directly in the chart.

To view the breakdown, scroll down below the chart. 

In the **WIP Aging chart**, there are two separate Breakdowns and corresponding [Issue lists](https://brokenbuild.atlassian.net/wiki/spaces/WIP/pages/4527423860):

1️⃣ For items displayed on the chart - currently in progress:

2️⃣ For historical completed issues used as benchmarks for highlights - their scope can be configured in the [Highlights](https://brokenbuild.atlassian.net/wiki/spaces/WIP/pages/4799398012) menu:

![image-20260317-162647.png](media://0aed7548-fc20-4e79-8446-8240ae6dd1bb)

In the **WIP Run chart**, there is only one Breakdown and Issue list, which include all issues within the chart scope:

![image-20260317-163503.png](media://a36f0909-b566-4111-b94a-2add25a8194d)

> Macro (toc)

## How to read the breakdown table

- The chevron on top of the table shows the name of the selected time frame (e.g., *Mar 25*), helping you quickly identify the scope of the data:

![image-20260317-163623.png](media://d8f42186-174b-4ba9-8295-cc6ae92dbcc3)

- The table contains expandable rows for each data group shown in the chart (Statuses for the Aging chart and WIP metric for the Run chart). You can expand each row into two additional levels of detail (for example: **Status (1️⃣) → Issue types (2️⃣) → Assignees (3️⃣)**:

![image-20260317-163942.png](media://0b0ef005-3520-4421-a91b-48065960b0e3)

- At each level, click **Find issues** to view the corresponding issues in the [Issue list](https://brokenbuild.atlassian.net/wiki/spaces/WIP/pages/4527423860) below the chart.

![image-20260317-164132.png](media://99f28596-8207-4d65-8551-a59c32539a6a)

- You can expand or collapse all sections at once using **Expand all** / **Collapse all**. The chosen state is preserved when switching between chart bars or highlighted areas.

![image-20260317-164212.png](media://38b0f9fc-06c6-4f9a-8182-55493da0e5e4)

- Each metric row contains a table with a set of columns.

**WIP Aging chart (WIP Breakdown):**

- **Total count** – number of work items currently in progress within the selected segment
- **<85%, 85%–95%, >95%** – number of work items falling into the corresponding percentile ranges compared to the selected historical baseline

![image-20260317-164548.png](media://6ed70503-c717-4ef1-a430-d8f64bda651f)

**WIP Aging chart (Completed issues Breakdown):**

- **Total count** – number of completed work items in the segment
- **Min** – minimum age
- **85%** – 85% of completed items have an age below this value
- **95%** – 95% of completed items have an age below this value (upper percentile / outliers threshold)
- **Max** – Maximum age

![image-20260317-164650.png](media://f895ba3e-00d0-4580-ab21-b24c03f97b63)

**WIP Run chart:**

- **Total** – total number of work items in the segment
- **Trend** – change compared to the previous period
- **Statistics columns** – one column for each metric selected in the [Statistics](https://brokenbuild.atlassian.net/wiki/spaces/WIP/pages/4805853203) menu

![image-20260317-164740.png](media://82bd05a6-1664-45b7-8844-8200384be2c4)

## Nested breakdown

- Click the **Breakdown** button to set which fields are used for grouping.

![image-20260318-172451.png](media://7318e041-1b56-406a-9b31-6e5d8d8b0596)

- You can select up to **2 levels** of breakdown, based on **any Jira field**.

![Scroll.gif](media://0726319b-df19-4a9e-ba80-5363ef354595)

- Drag fields to reorder the first and second levels.

![drag.gif](media://f55d5d82-fff6-4638-aed3-53a6cc03e35f)

- Click **Reset** to return to the default suggested view.

![image-20260318-173431.png](media://95778560-952b-4b25-9814-7fd79761ecf8)

- For nested levels, the **Total** column displays both the numeric value and the percentage of the parent total (1️⃣). Sparkbars (2️⃣) help to visually compare proportions.

![image-20260318-173538.png](media://7de125bb-a3b5-4dd6-b501-87ad1d19b333)

## Possible breakdown configurations

### By Board (team)

When multiple teams collaborate on a major release, for example, segmenting metrics by boards (teams) is essential. This allows you to examine individual team data alongside aggregate values, providing insights into anomalies and trends. 

> 📝 This option is available only for charts that use boards (Scrum or Kanban) as a data source.

### By Project

Whatever the data source you use, whether it be boards or a JQL filter, you can view the work distribution by projects. This provides perspective on the ratio between projects and the ability to spot unexpected results.

### By Issue type

Jira standard issue types usually represent different types of work: a Story is about delivering value to the end user, a Bug is for fixing what is broken, and a Task is used for additional technical efforts that do not directly impact the user. Having metrics broken down by issue type provides additional context for interpreting the results of a sprint or interval.

### By Status

At any given moment, every issue has a status that defines its progress and place in the work funnel. You can determine the readiness of remaining work using breakdown by status.

### By Priority

Segmenting your results, changes, or remaining work by priority provides insight into what’s happening, especially when combined with other breakdown options.

### By Assignee

An individual perspective allows you to see how work is distributed among assignees, regardless of the data source selected for the chart.

### By Epic (Parent)

Epics are often used as a container for stories to group them by a common topic or place in a product, such as *Sign up* or *Onboarding*. Therefore, having work segmented by Epics is beneficial for analyzing team focus and resource allocation.

### By Release (Fix Version)

Releases are the main points of synchronization within and among teams because they frame the delivery around the goal to release some value to users. A breakdown by releases provides a helicopter view of all work in the sprint or time interval.

### By Label

Labels are the most flexible option for distinguishing one type of work from another, making the breakdown by labels proper indeed.

### By Creator

Breaking down issues by the Creator field provides a reliable historical record of who created each issue, enhancing security and accountability by ensuring the original author is always logged, even if reporting responsibility shifts.

### By Reporter

Using the Reporter field for breakdowns allows you to track the current responsibility for each issue. This offers dynamic reporting that reflects the current state of issue ownership and helps manage workloads effectively.

### By Resolution

Breaking down issues by the Resolution field in Jira provides valuable insights into the outcomes of tasks, allowing for a clearer understanding of task closure reasons and overall project progress.

### Many more

You can break down by any Jira field available in your instance, whether it’s built-in or tailored for your process. For example:

- **Component** – product area or subsystem.
- **Environment** – staging, production, mobile, web, etc.
- **Due Date / Target Date** – delivery or compliance deadlines.
- **Program Increment / Value Stream / ART** – common in SAFe setups.
- **Business Value / WSJF factors** – prioritization and portfolio metrics.
- **Severity / Impact / Risk Level** – often used for bug tracking or compliance.
- **Custom labels, tags, or categories** – any field that helps segment your work.

Experiment with different options to discover the insights most valuable for your team.