Progress indicators

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 Issue 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 project, where each slice represents a project.

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

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

In the above screenshot, eight progress indicators are shown.

• Each indicators lists the issue 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 issue count for each field value shown in the indicator.

The indicators are defined as follows:

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

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

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

4. Fix Version: Shows the issue count for each fix version. The screenshot above shows 15 issues assigned to fix version.

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

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

7. Sprint: Shows the issue count for each sprint, including closed sprints, the active sprint, and the backlog. An issue 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 issues assigned to a closed sprint, 16 issues assigned to the active sprint, and 26 issues assigned to the backlog.

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

8. Project: Shows the issue count for each project.
   Project Category (not shown): Shows the issue count for each project category. Project categories are defined in project settings and are used to group related projects, for example by department (such as Marketing or Human Resources) or by budget classification (such as Operational Expense or Capital Expense).

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

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 issue 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 issues (issues with a Status Category of Done) by the total issue count.

Completion Rate = [Resolved Issues/ Total number of issues] x 100%

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

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

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

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

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

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

Completion by Time = (Completed issues / 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 issues out of a total of 279.25 hours (=154.75 + 80.5 + 44).

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

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

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

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

Story Points Progress = [ Story Points for Resolved Issues/ Total Story Points]

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

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

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

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%

3. 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%

4. 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 issue'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%

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 Issue 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 projects included in the report.

2. ∑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 project by dividing the Original Estimate by the sum of Time Spent and Remaining Time for that project.

Time in Status can be measured in four ways.

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

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

2. Time in Progress: This measurement shows how long an issue 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 issue moves to Done.

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

3. 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.

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

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

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

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

For example, 399 issues have breached the Time to First Response target, and 860 issues 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 issues that failed to meet their target in any SLA cycle.

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

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

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

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

5. Time to Resolution: This indicator shows issues whose Time to Resolution SLA is in a Breached, Paused, or Completed state.

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

7. Time to Resolution: Met vs Breached: This indicator returns issues that either met or failed to meet their Time to Resolution target.

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

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 Issue 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 issues 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 issue has 4 Double points out of 22, which means that 18% (=4 / 22) of the Double points have been resolved.

3. 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 Issue Structure tab, as shown above.

4. 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.

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

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

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

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

They can also display a horizontal stacked bar that summarizes progress for a field. For example, the Issue Type indicator shows the issue count for each issue 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 Issue Count, making it easier to identify trends and relationships in your data. To learn more about charts, refer to the related article.

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.

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

1. Assignee: Shows the issue count for each assignee, including unassigned issues.

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

2. Fix Versions: Shows the issue count for each fix version, excluding issues that do not have a fix version.

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

3. Components: Shows the issue count for each component, such as Web, Integration, or Design, excluding issues that do not have a component.

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

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

For example, an issue can be assigned to multiple fix versions. If an issue 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 issues represented by the indicator remains 15 because the same issue 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.

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.