When analyzing delivery data, it is essential to segment it by meaningful issue field values to gain deeper insights into trends and anomalies. To view the breakdown, select a specific sprint or interval on the Velocity chart, then scroll down to the breakdown section.

Open

This powerful tool is available for all Burnup and Burndown charts (except the Sprint Burndown Chart). By providing detailed breakdowns, it offers new insights into completed work and progress, helping you use these forecast charts more effectively.

Open

You can change the breakdown configuration in the chart settings to apply it to all users with whom the chart is shared or on an individual level in the breakdown user preferences:

You can swiftly expand and collapse all breakdown sections without doing it one by one.

Sparkbars (horizontal bars) provide a visual and percentage comparison of each segment within the parent segment or metric:

To find out how to manage the appearance (on/off, color, order) of metrics displayed on the chart and breakdown, please read this article.

By Board (team)

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

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 velocity 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. For example, you can determine the readiness of work not completed at the end of the sprint using breakdown by status:

By Priority

Segmenting your commitments, changes, and results by priority provides insight into what’s happening, especially when combined with other breakdown options:

By Rollover count

When an issue rolls over from one sprint to another, it’s beneficial to know how many times it has rolled over and how many other issues do the same:

By Assignee

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

Releases are the main points of synchronization within and among teams because they frame the delivery around its 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 Component

Components are effective for segmenting issues across organizational, process, and product parameters. If you use components in your workflow, you can also use them when analyzing delivery data:

By Label

Labels are the most flexible option for distinguishing one type of work from another, making the breakdown by labels useful 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.