Pivot

You can create a report for a Board’s Backlog and then use the Pivot tab to group issues by priority, remaining effort, assignee, and status. To reproduce this report, you can use the example shown in the screenshot or create your own report from a board on the demo site.

The grouping in the Pivot tab lets you see the remaining effort for each deliverable by assignee. This helps you identify whose backlog contains the most urgent work and estimate how likely it is to be completed in upcoming sprints.

For example, one team member may need two days to complete a highest-priority issue before starting another high-priority task. Based on this insight, you may choose to reassign the second task to another team member so work can begin sooner when it moves into a sprint.

Using the Pivot tab also removes the need to add Remaining Estimate to the card layout in your Board settings for backlog refinement. You can update and reassign issues directly from the issue view by selecting items in the Summary section of the tab. After making changes, you can refresh the report without reloading the entire page.

Yes. You can display progress indicators as values. In the example above, Spent vs Estimated is used to show how much time was spent compared to the original estimate for each issue type and release.

This indicator appears as a horizontal stacked bar. Time spent is shown in green as long as it remains within the original estimate, while the remaining time is shown in grey. When the estimate is exceeded, the overspent portion appears in red, and the green segment decreases proportionally relative to the total time spent.

To recreate this report, you can follow the example on the demo site. For more details on available progress indicators and their definitions, refer to the related article.

You can display the table outside the report in several ways.

For example, the contents of the Summary section from the Pivot tab type can be shown on a dashboard using gadgets, as described in a separate article. To embed a report in a Confluence page, refer to this related article.

You can use this tab to measure the average time spent is shown for a repetitive task occurring in every Fix Version, such as a setup, merging, and packaging activity.

Yes. You can use the % Row to identify which Fix Versions and Epics have the highest share of time spent on resolving bugs rather than on development work.

In the example above, 7% of the time in Version 1.0 was spent on bug resolution. In comparison, 11% of the time was spent on bugs without a version, which were likely removed from a previous version and moved to the backlog for reassignment.

Yes. You can select the same field for both Rows and Columns.

Doing so will result in duplicated data. For example, if Time Spent is set as the Values field, using the same field for Rows and Columns can help you understand how your Jira data is displayed in the Summary section.

This approach is often useful as a learning step before adding different fields to Rows and Columns.

Yes. Rows and Columns can contain blank values.

When a value is missing, it can appear in different forms depending on the field used. For example, if you set Issue and Assignee as either Rows or Columns, issues without an assigned user will appear as Unassigned.

Similarly, if you set Project and Fix Version/s as either Rows or Columns, issues that are not linked to any version will appear as None.

Rollup fields—such as ∑ Original Estimate, ∑ Time Spent, and ∑ Remaining Estimate—available in Jira’s Issue Navigator can also be displayed as values in the Summary section when using the Summation function (for example, shown as Original Estimate SUM in the screenshot above).

However, only standard fields—such as Original Estimate, Time Spent, and Remaining Estimate—can be displayed in the Breakdown section (for example, shown as Estimated).

No. You cannot display an issue where multiple users have logged work in the Pivot tab type. In this tab type, the current assignee can be used as a field in Rows or Columns, but assignee history is not available in reports.

As shown in the example above, when Jira’s default time tracking is enabled and the Worklogs/Comments tab type is used, set Issue Type and Assignee as columns and User as rows. This will allow you to see whether a user logged time on issues they are or are no longer assigned to within the selected time period.

Yes. You can sort and rearrange columns within the Breakdown section by following the steps mentioned in a related article.

Yes. You can sort the Issue Count and Row Total columns in the Summary section by following these steps:

1. Open Column display options and choose whether to hide Issue counts, row totals, or leave both visible.

2. In the Values dropdown, select the field you want to use for the Row Total column.

3. To sort the Row Total column, click its column header. In the example, the Time Logged is not currently sorted.

4. To sort the Issue Count column, click its column header. In the example, this column is not currently sorted. In the example, Issue Count is sorted in ascending order, indicated by an upward arrow (↑)

If the Pivot tab is missing, it may have been removed from the report.