Pivot Report

Progress indicators

Group 556 (1)-20260626-200256.png

This article explains why and how to use progress indicators multiple sections of reports.

To test which indicators best fit your spaces, try this demo.

Why should you use the app’s progress indicators?

Compared to the default indicators available in Jira, the app's progress indicators provide deeper insights into your data.

  • Flexible metrics: Show space-level progress using Story Points, work item status, or time-based system fields.

For example, you can display progress show the count of story points of resolved work items and compare them to the total amount of points, for each space or all spaces in a report.

  • Derivative fields: Show the difference between time-based system fields using progress indicators, such as Estimate Accuracy, without creating custom fields in Jira or automations to calculate and store these values.

For example, Estimate Accuracy is calculated by dividing the Original Estimate by the sum of Time Spent and Remaining Time within the report.

  • Compact charts: Display which value is more frequent for a system field, without using JQL or a dashboard gadget.

For example, each value is represented by a segment of a horizontally stacked bar chart. The length of each is segment reflect the amount of work items compared to the whole.

  • Targeted search: Click on a segment of the bar chart to locate and edit work items individually or in bulk.

  • Customized indicators: Create custom number fields and display them as progress indicators.

How do Jira’s default progress indicators compare?

Group 572 (1)-20260709-040446.png

You can display Time Progress (or ∑Progress) in the Issue Navigator or by using one of the app's progress indicators, where it is available under a different name. This indicator takes into account lower hierarchy levels, including child work items such as sub-tasks.

Time progress (or ∑Progress) = [Spent Time / (Spent Time + Remaining Time)] × 100%

In the Issue Navigator, you can use this indicator to show the cumulative progress of an epic and its child work items. However, the Issue Navigator cannot display cumulative progress for an entire space.

Reports generated by the app support space-level cumulative progress, whereas Jira's default indicators do not.

Group 572 (6)-20260710-011114.png

Compared to the Issue Navigator, the Work item View lets you display Time Progress alongside other Jira progress indicators. The available indicators are described below.

  1. Progress (work item count): Shows how a work item is progressing based on the status category of the work items directly beneath it. This indicator is available in Jira's Work item View and Advanced Roadmaps. It does not take lower hierarchy levels, such as child items, into account.

In the above example, the indicator shows 50% complete based only on the two tasks shown in the table, where one task is In Progress and the other is Done. If either task had sub-tasks, their statuses would not affect the indicator.

  1. Time Progress (or ∑Progress): Shows how much work has been completed based on Time Spent divided by the sum of Time Spent and Remaining Time, while taking lower hierarchy levels, including child items, into account. When a work item is resolved, the indicator shows 100% progress.
    In Advanced Roadmaps, this indicator is named Progress (estimate) and can be configured to show the rate of completion based on Story Points instead of estimates.

In the above example, a parent work item shows 88% ∑Progress when the Time Spent and Remaining Time of its child items are included. The same work item shows 99% Progress when only its own Time Spent and Remaining Time are considered.

  1. Time tracking bar: Shows the Original estimate, Time Spent and Remaining Time for a work item. It is available in the work item details panel (shown in the screenshot as a pinned field for convenience).
    The time tracking bar does not take lower hierarchy levels, such as sub-tasks, into account. In addition, it is limited to 100 child items. If an epic has more than 100 child items, such as stories or bugs, any additional child items are not included in the calculation.

In the above example, the bar displays the Time Spent and Remaining Time for the two tasks shown in the table. If either task had sub-tasks, their estimates and logged time would not affect the bar.

Reports generated by the app provide alternatives to the Progress (work item count) indicator that take lower hierarchy levels into account and can be configured to exclude parent work items.

Compared to Progress (estimate), the app's progress indicators can also be configured to show progress based on Story Points instead of estimates.

In addition, the app's progress indicators are not subject to the same limitations as the Time Tracking bar. They can also show whether estimates are accurate or whether work has exceeded the original estimate.

Features and use cases

Display a Story Points in a slice, progress indicator, and column
Group 565 (3)-20260708-002710.png

In the above screenshot, the two indicators, Time Spent and Story Points, are shown in the Slices section, Progress section, and Summary section of the Work item Structure tab type. In other tab types, they are also shown in the Breakdown section.

The Story Points field behaves as an indicator or rollup field depending on the section.

  1. Slices: Story Points is configured in the report sidebar to behave as a rollup field (Summation function). The sum of Story Points is shown for each space, where each slice represents a space.

  2. Progress indicator: Story Points behaves as a single-value indicator that shows the sum of Story Points for all spaces included in the report.

  3. Rollup: Story Points behaves as a rollup field that displays the sum of Story Points for each space.

Time Spent is an indicator calculated based on the cumulative sum of all worklogs. It represents how much of the Original Estimate has been consumed. In comparison, Story Points is an indicator calculated based on the cumulative sum of story points.

In the example shown, the Time Spent indicator represents the cumulative sum of Time Spent across the three spaces included in the report: 188.75 hours (71 + 78.25 + 39.5).

The Story Points indicator represents the cumulative sum of story points across the three spaces included in the report: 12 points (5 + 7).

Display the issue count for system fields
Group 557-20260630-040543.png

In the above screenshot, eight progress indicators are shown.

  • Each indicators lists the work item count for a single system field, such as Assignee, including cases when a single field can hold multiple values, such as a Sprint (which can hold the value of closed sprints and the active sprint).

  • Each indicator is displayed as a horizontal stacked bar of equal length. The length of each segment varies according to the work item count for each field value shown in the indicator.

The indicators are defined as follows:

  1. Work item Type: Shows the work item count for each work item type, such as Bug, Epic, Story, Sub-task, or Task.

  2. Assignee: Shows the work item count for each assignee, including unassigned work items. The screenshot above shows 51 work items, of which eight are unassigned. The remaining work items are assigned to one of four users.
    Reporter (not shown): Shows the work item count for each user who created a work item included in the report.

  3. Status: Shows the work item count for each status, including custom workflow status, such as Waiting for Support.
    Epic Status (not shown): Shows the work item count of epics grouped by status.
    Status Category (not shown): Shows the work item count for each status category, such as To Do, In Progress, and Done.

  4. Fix Version: Shows the work item count for each fix version. The screenshot above shows 15 work items assigned to fix version.

  5. Component: Shows the work item count for each component, such as Web, Integration, or Design. If a work item has multiple components, it is counted once for each assigned component. The overall work item count remains unchanged.

  6. Priority: Shows the work item count for each priority, such as Highest, High, Medium, Low, and Lowest.
    Parent Priority (not shown): Shows the work item count of parent work items grouped by priority.

  7. Sprint: Shows the work item count for each sprint, including closed sprints, the active sprint, and the backlog. A work item that spans multiple sprints, such as one that started in a closed sprint and remains in the active sprint, is assigned to both sprint values.

The example above above shows 13 work items assigned to a closed sprint, 16 work items assigned to the active sprint, and 26 work items assigned to the backlog.

Sprints Without Closed (not shown): Shows the work item count for sprints that are not closed, including the active sprint and the backlog.

  1. Space: Shows the work item count for each space.
    Space: Category (not shown): Shows the work item count for each space category. Space categories are defined in space settings and are used to group related spaces, for example by department (such as Marketing or Human Resources) or by budget classification (such as Operational Expense or Capital Expense).

  2. Link (not shown): Shows the work item count for a link type. For example, the Is blocked by link progress indicator shows the number of blocked work items and the work items that are blocking them.

Additional system fields and user-created custom fields are supported as progress indicators. If the field you need is not available, please contact our support team by email or through the service desk.

Display completion based on estimates (%) or Story Points (fraction)
Group 569-20260709-023215.png

In the above screenshot, three indicators, Completion Rate, Completion by Time, and Story Points (Progress), are shown.

Each indicator is displayed as a horizontal stacked bar of equal length. The length of each segment varies according to the work item count, hours, or Story Points for each Status Category, depending on the indicator.

The indicators are defined as follows:

  1. Completion Rate is an indicator calculated by dividing the count of resolved work items (work items with a Status Category of Done) by the total work item count.

Completion Rate = [Resolved Work items/ Total number of work items] x 100%

In the example shown, 44% (=11 / 25) of work items are completed, based on 11 work items with a Status Category of Done out of a total of 25 work items.


  1. Completion by Time is an indicator calculated by dividing the cumulative time for completed work items by the total time, which consists of the following elements:

Completed work items: Time Spent and any Remaining Time for resolved work items (work items with a Status Category of Done).

In Progress work items: Time Spent and Remaining Time for work items with a Status Category of In Progress.

To Do work items: Time Spent and Remaining Time for work items with a Status Category of To Do.

Total time: The cumulative sum of time for Completed, In Progress, and To Do work items.

Completion by Time = (Completed work items / Total Time) × 100%

In the example shown, 55% (=154.75 / 279.25) of the Total Time, based on 154.75 hours logged (and remaining unspent time) for completed work items out of a total of 279.25 hours (=154.75 + 80.5 + 44).

Remaining unspent time: This value represents remaining time on closed work items where it was not reset to zero upon resolution or not manually updated.

  1. Completion by Estimate is an indicator calculated by dividing the Original Estimate of resolved work items (work items with a Status Category of Done) by the total Original Estimate.

Completion by Estimate
= [Original Estimate of Resolved Work items/ Total Original Estimate] x 100%

In the example shown, 38% (=93 / 244) of work items are completed, based on 93h Original Estimate for work items with a Status Category of Done out of a total of 244 hours (=93 + 107 + 44).


  1. Story Points Progress is an indicator calculated by dividing the sum of Story Points for resolved work items (work items with a Status Category of Done) by the total Story Points.

Story Points Progress = [ Story Points for Resolved Work items/ Total Story Points]

In the example shown, 7 / 12 of the Story Points are achieved, based on 7 Story Points completed for work items with a Status Category of Done out of a total of 12 Story Points.


  1. Story Points Rate (not shown) is an indicator calculated by dividing the sum of Story Points for resolved work items (work items with a Status Category of Done) by the total Story Points.

Story Points Progress = [ Story Points for Resolved Work items/ Total Story Points] × 100%

Display estimate accuracy, overspent, and Time Progress
Group 558-20260630-040823.png

In the above screenshot, four progress indicators, Spent Vs Estimated, Time Budget, Estimate Accuracy, and Work Ratio, are shown. These indicators are derived from four Jira system fields: Original Estimate, Time Spent, Time Remaining, and Status Category.

The indicators are defined as follows:

  1. Spent VS Estimated: This indicator lets you view the percentage of time already used.
    If you exceed the initially estimated time in the Original Estimate, the Spent VS Estimated percentage will surpass 100%.

  2. Estimate Accuracy is calculated by dividing the Original Estimate by the sum of Time Spent and Remaining Time. This indicator measures how accurately work was estimated before it began by showing the combined effect of overestimating and underestimating effort.
    A value below 100% indicates that the original estimate was not accurate. For example, a value of 90% means the estimate was 90% accurate.

IF Spent Time+ Remaining Open > Original Estimate
THEN Estimate Accuracy = [Original Estimate / (Spent Time + Remaining Open)] × 100%

IF Spent Time + Remaining Open < Original Estimate
THEN Estimate Accuracy = [(Spent Time + Remaining Open) / Original Estimate] × 100%

Remaining Open represents the total Remaining Time across all work item that are currently in the To Do or In Progress status categories.


  1. Time Budget is calculated by dividing the sum of Time Spent and Remaining Time by the Original Estimate. This indicator measures whether work is staying within the planned budget.
    A value above 100% indicates that the estimate has been exceeded. For example, a Time Budget of 110% means the original estimate has been exceeded by 10%.

Time Budget = [(Spent Time + Remaining Time) / Original Estimate] × 100%


  1. Work Ratio is calculated by dividing Time Spent by the sum of Time Spent and Remaining Time, similarly to Jira's Time Progress field. This indicator measures progress rather than estimate accuracy or budget overruns. It shows how much of the current scope has been completed relative to the work that remains.
    If the remaining time is increased during the work item's lifecycle, the calculation automatically reflects the revised scope.
    For calculation examples, including an example of how the Status Category affects the indicator, refer to the related article.

Work Ratio = [Spent Time / (Spent Time + Remaining Time)] × 100%

This indicator is available after installing the app and differ from the default Work Ratio available in the Issue Navigator.

Jira’s default Work Ratio measures progress by dividing Time Spent by the Original Estimate. This calculation applies only to the work item itself and does not include data from child items.

Display estimate accuracy as a progress indicator and column
Group 566 (1)-20260708-025127.png

In the above screenshot, the three indicators, Time Spent, Story Points, and Estimate Accuracy, are shown in the Progress section and as rollup fields in the columns of the Summary section of the Work item Structure tab type. In other tab types, they are also shown in the Breakdown section.

The Estimate Accuracy indicator and rollup field are defined as follows:

  1. Estimate Accuracy is an indicator calculated by dividing the Original Estimate by the sum of Time Spent and Remaining Time. It measures how accurately work was estimated before it began by showing the combined effect of overestimating and underestimating effort.

In the example shown, the indicator represents the combined Estimate Accuracy across the three spaces included in the report.

  1. ∑Estimate Accuracy is both an indicator and a rollup field available for every row in the Summary section.

In the example shown, the rollup field displays the Estimate Accuracy for each space by dividing the Original Estimate by the sum of Time Spent and Remaining Time for that space.

Display Time in Status as a column indicator
Group 522-20260528-015419.png

Time in Status can be measured in four ways.

  1. Time in To Do: This measurement shows how long a work item remains in the To Do status category, starting from the Created date until the current date and time. The value stops increasing when the work item moves to either In Progress or Done.

In the example above, the work item spent more than three weeks in the To Do status category.

  1. Time in Progress: This measurement shows how long a work item remains in the In Progress status category, starting from the moment it enters that category until the current date and time. The value stops increasing when the work item moves to Done.

In the example above, the work item has spent more than one week in the In Progress status category to date.

  1. Time in Status: This measurement displays a horizontally stacked bar that shows how much time elapsed between each status transition. The total time appears in a tooltip when you hover over or click the bar.

In the example above, the right segment represents Time in To Do, while the left segment represents Time in Progress.

  1. Time in Status Group (not shown): This measurement displays a horizontally stacked bar that shows how much time elapsed within each status category.

To learn more about Time in Status, refer to the related article.

Display indicators withing as dashboard gadgets
Group 565 (4)-20260708-004729.png

Use the Pivot Report Progress gadget to display progress indicators on Jira dashboards in both Cloud and Data Center.

Measure SLA within indicators in JSM projects
Group 534-20260624-002719.png

The app supports the following Jira Service Management (JSM) progress indicators:

  1. SLA Breached: This indicator returns the list of work items whose current or most recent SLA cycle failed to meet its target.

For example, 399 work items have breached the Time to First Response target, and 860 work items have breached the Time to Resolution target.

The SLA Ever Breached indicator is also available, although it is not shown in the example. It returns work items that failed to meet their target in any SLA cycle.

  1. Time to First Response: This indicator shows work items whose Time to First Response SLA is in a Breached, Paused, or Completed state.

For example, 993 of 1,392 work items were completed and met the target, 340 work items breached the target, and 59 work items were paused.

  1. Time to First Response: Met vs Breached: This indicator returns work items that either met or failed to meet their Time to First Response target.

For example, 399 work items (340 breached work items and 59 paused work items) failed to meet the target, while 994 work items (993 completed work items and 1 successful cycle) met the target.

  1. Time to Resolution: This indicator shows work items whose Time to Resolution SLA is in a Breached, Paused, or Completed state.

For example, 525 of 1,392 work items were completed and met the target, 766 work items breached the target, and 101 work items were paused.

  1. Time to Resolution: Met vs Breached: This indicator returns work items that either met or failed to meet their Time to Resolution target.

For example, 884 work items (766 breached work items, 101 paused work items, and 17 failed cycles) failed to meet the target, while 537 work items (525 completed work items and 12 successful cycles) met the target.

Display the cumulative sum for a formula or custom field
Group 602-20260808-020217.png

In the example above, the Double points formula field is shown in three report sections. This field is calculated by multiplying the Story points estimate value, which can be set in the Work item view.

The formula field is available in the following sections:

  1. Slices: The rollup value of the field is shown for each status category.
    For example, To Do work items have a total of 12 Double points.

  2. Progress indicators: The field can be used in up to three progress indicators.
    A single-value indicator can show the sum of Double points (22 Double points) for all projects included in the report.

    You can also show the number of Double points completed relative to the total as a fraction or percentage. In this example, one resolved work item has 4 Double points out of 22, which means that 18% (=4 / 22) of the Double points have been resolved.

  1. Breakdown: The field's value, rollup value, or rollup value by status category can be shown as a column in the Breakdown section of any tab type except Charts. It can also be shown in the Summary section of the Work item Structure tab, as shown above.

  2. Summary: (not shown) In the Summary section of the Pivot tab type, Double points can be shown as a value in a row or as a rollup sum in each cell of a pivot table.

You can also display a Jira custom field by using the Number field type instead of a formula field type. The value of this custom field is set in the Work item view.

How can you display progress indicators?

You can display indicators in the progress section by following these steps:

  1. Click the Progress dropdown.

  2. Select the indicators you want to display.

  3. (Optional) After selecting indicators, you can reorder them by hovering over an indicator name and using the grip icon that appears.

Why should you use indicators in widgets?

Widgets become available after the app is installed in your Jira Cloud instance.

Display the hierarchy without leaving the Work item view

Widgets give you a complete view of the work item hierarchy, unlike Jira’s default Work item View—especially for container work items like Epics.

Group 240-20260106-041739.png
  1. Jira’s table of child-level items shows only part of the hierarchy, leaving out sub-tasks.

Group 239-20260106-041531.png

In addition to showing the full hierarchy, the Work Item Tree widget can be configured to display how each item contributes to the overall work.

  1. This contribution can appear as numeric time-tracking values or as visual progress indicators—information that is not available in the default Work item view.

Measure how each work item contributes to your Space goals

Widgets provide a complete view of progress indicators.

Group 239 (1)-20260106-043501.png
  1. Jira’s table of child-level items is limited to showing a completion rate based on status for only it’s child items, excluding sub-tasks.

Group 240 (2)-20260106-043854.png
  1. The Work Item Progress widget can display the completion rate and other progress indicators for all work items in the hierarchy, including sub-tasks.

Preview a report before creating it

Widgets give you the means to preview report contents (e.g. the Summary sections for the Progress and Work item Structure tabs) directly from the Work item view.

FAQ

Can you exclude Parent issues and change how the Completion rate is calculated?
Group 565 (1)-20260707-234026.png

Yes. You can change how progress is calculated for the Completion rate progress indicator.

For instructions, follow the steps described in the separate article.

Can you show the Satisfaction rating as an indicator?
Group 565-20260707-233507.png

Yes. You can display the Satisfaction rating as a progress indicator for a Jira Service Management (JSM) space, as described in the related article.

Can you filter progress indicators using slices?

Yes. Progress indicators are updated based on the selected slice.

To configure how slices affect progress indicators, follow the steps described in the related article.

How are progress indicators different from charts?

Progress indicators display a single rollup numeric value, such as Story Points, Time Spent, or Work item Count.

They can also display a horizontal stacked bar that summarizes progress for a field. For example, the Work Type indicator shows the work item count for each work type.

Charts can also display horizontal stacked bars, along with other chart types, including vertical bar, line, pie, polar area, radar, and bubble charts.

In addition, charts let you compare up to two fields simultaneously, such as Time Spent and Work item Count, making it easier to identify trends and relationships in your data. To learn more about charts, refer to the related article.

What is the difference between Time Spent and Time Logged?

Time Spent represents how much of the original estimate has been consumed. It is mainly used as a progress indicator to show how much work has been completed relative to what was planned.

Time Logged represents the actual work recorded by users during a specific period. You obtain Time Logged by filtering Time Spent using a defined time interval.

For example, if you want to see how much time was logged during the last sprint, you can set an interval that matches the sprint’s start and end dates. The filtered result shows the time logged only within that period.

Troubleshooting

Why aren't the indicator values adding up to the expected issue count?
Group 567 (2)-20260708-230134.png

In the above screenshot, three indicators, Assignee, Fix Versions, and Components, are shown. The total work item count for two of these indicators does not match the expected All Issues value of 51, as explained below.

  1. Assignee: Shows the work item count for each assignee, including unassigned work items.

In the example shown, all 51 work items are included. Eight work items are unassigned, and the remaining work items are assigned to one of four users.

  1. Fix Versions: Shows the work item count for each fix version, excluding work items that do not have a fix version.

In the example shown, 15 work items =(5 + 4 +6) have at least one fix version.
The remaining 36 work items (=51 - 51) do not have a fix version and are therefore not included in the indicator.

  1. Components: Shows the work item count for each component, such as Web, Integration, or Design, excluding work items that do not have a component.

In the example shown, 18 work items (=8 + 5 + 5) have at least one component.
The remaining 33 work items (=51 - 18) do not have a component and are therefore not included in the indicator.

These examples show that the work item count displayed by an indicator can be lower than the total work item count for the report.

In contrast, the cumulative work item count across the individual values within an indicator can exceed the indicator's total work item count.

For example, a work item can be assigned to multiple fix versions. If a work item that is already assigned to Version 1.0 is also assigned to Version 1.1, the count for each version increases independently.

The count for Version 1.0 could remain at 5, while the count for Version 1.1 increases from 4 to 5. However, the total number of work items represented by the indicator remains 15 because the same work item is counted only once in the overall total.

As a result, the total length of the horizontal bar remains unchanged, while only the relative size of each segment changes.

Why can't you see progress indicators?

If progress indicators do not appear, verify that the Progress section is enabled by following these steps:

  1. Click Configure in the header.

  2. Select Current tab from the drop-down list.

  3. Confirm that Show progress is selected.

  4. Ensure that at least one progress indicator is selected in the Progress section.

If Show progress is not enabled, progress indicators will not be displayed in any tab type.

If you have questions or need assistance, contact our support team via email or service desk. Our team is available Monday through Friday (9:00 AM to 7:00 PM GMT+7) to help with technical challenges or discuss improvements.