Pivot Report

Using the 'Manage Pivot Reports' page

Group 431-20260316-235442.png

This article explains how to create a report using a button on the Manage Pivot Reports page, where you can also view all reports accessible to your account.

Why should you use this page?

You can use the Manage Pivot Reports page to create reports. This method is useful when you want full control over the report’s source during creation, while still using the creation options available in the Issue Navigator or an Agile Board.

You can also use this page to locate reports you have permission to view and identify reports that overlap in source or name.

Features and use cases

Reference multiple projects when creating a report.
Group 432 (1)-20260317-004430.png

When you click Create Report on this page, the Create New Report pop-up appears.

You can use this pop-up to include multiple projects by entering JQL, as shown in the screenshot above, or by selecting a filter.

For example, the Cross Project demo report shown in the screenshot below is based on a JQL query that references three projects. The report sidebar also shows the same projects that appear in the pop-up above.

Group 393-20260306-041059.png

You can achieve similar results by using a Board or the Issue Navigator as the source if it references multiple projects through JQL or a filter.

In comparison, using the Manage Pivot Reports page helps you check whether another report already exists with the same source or name that you can access. If a report uses a similar source, you can copy it from this page. The copied report is already configured and may highlight insights from a previous analysis based on the same source.

Group 432 (3)-20260317-012150.png

The steps to find existing reports are described in the related article.

How can you access this page to create a report?

The Manage Pivot Reports page can be accessed from Jira’s top navigation bar. On this page, use the button to create a report.

  1. Click on Pivot Reports in the top navigation bar.

  2. Select Manage Reports.

  3. On the right-hand side, click Create Report.

Group 324 (1)-20260303-025743.png
  1. In the Create New Report pop-up, select a Source type.

  2. Optionally, check the boxes to include parent and child issues in the report.

  3. Click Create.

Group 324 (2)-20260303-030103.png

What source types can you use to create a report?

In the Create New Report pop-up, shown in the previous section, you can select one of six available source types to create a report from the Manage Pivot Reports page:

Project

  1. Set the Source type to Project.

  1. Select the project to be referenced in the report.

  2. Optionally, check Exclude resolved issues to exclude issues with the status category ‘Done’ in the report.

  3. If needed, check the boxes to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  4. Click Create.

Group 131-20250801-135903.png

Board

Kanban Board

  1. Set the Source type to Board.

  2. Select the board to be referenced in the report.

  3. Optionally, select work items from the Board to filter issues for the report. The report will include:

    • Work items not listed in the Kanban backlog.

    • Work items listed in the Kanban backlog.

    • All work items.

  4. If needed, check the boxed to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  5. Click Create.

Group 207-20251002-000530.png

Work items in the Unmapped statuses column will not appear in the report, as mentioned in a related article.

Scrum Board

  1. Set the Source type to Board.

  2. Select the board to be referenced in the report.

  3. Optionally, select all applicable sprints from the Board to filter issues for the report. The report will include:

    • Work items from active sprints (one or multiple).

    • Work items from all future sprints following the active sprint.

    • All active work items not assigned to an active or future sprint.

    • Work items from the two most recently closed sprints.

    By default, Active Sprints is selected and greyed out. It can be unchecked once another option is chosen.

  4. If needed, check the boxed to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  5. Click Create.

Work items in the Unmapped statuses column will not appear in the report, as mentioned in a related article.

Group 132-20250801-140026.png

Service Queue

  1. Set the Source type to Service Queue.

  2. Select the Jira Service Management project to be referenced in the report.

  3. Select a Queue. The default three queues for a Service Project are All My Tickets, All Open Tickets, and Open Tasks.

  4. If needed, check the boxed to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  5. Click Create.

Group 133-20250801-140154.png

Saved Filter or Issue

Saved Filter

  1. Set the Source type to Saved Filter.

  2. Select the filter to be referenced in the report.

  3. If needed, check the boxed to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  4. Click Create.

Group 134-20250801-140315.png

Issue

  1. Set the Source type to Issue.

  2. Select the issue to be referenced in the report.

  3. If needed, check the boxes to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  4. Click Create.

Group 135-20250801-140449.png

JQL / Search results

  1. Set the Source type to JQL / Search results.

  2. Enter the JQL query to be used in the report.

  3. If the query is valid, a green checkmark will appear (see screenshot).

  4. To troubleshoot the query in the Issue Navigator, click the Search link and follow the steps in a related article.

You cannot create the report until the query is considered valid.

  1. If needed, check the boxed to include parent and child issues to extend the report, which are defined by Atlassian in a related article.

  2. Click Create.

Group 136-20250801-141152.png

Will you need to save the created report?

When you create a new report from the Manage Pivot Reports page, a saved report is created alongside its unique ID. In contrast to the other methods, the created report only needs to be saved after you apply additional changes to it.

FAQ

What is the report's name and description when using this method?

The source type used to create a report determines its name and description. The results for each method are listed in the related article.

Can you further filter the contents of a report source?

Yes. If you need to further filter the extended contents or to modify the report source, refer to the steps outlined in a separate article.

How can you show the entire issue tree when creating a report?

You can show an entire issue tree by creating a report that references a parent issue in a standard Jira hierarchy, such as Epic > Story > sub-task.

If the issues are connected through relationship links instead, such as an Epic being blocked by an Initiative, you can create a custom hierarchy within the report. This lets you show multiple Epics and their child issues under a common Initiative.

Create a report based on the Jira hierarchy

Use this method when you want to show all issues under a single parent, such as an Epic.

  1. Set Source type to Issue.

  2. Select the parent issue that you want to reference in the report.

  3. Check the box to child issues to extend the report,

  4. Click Create.


Create a custom hierarchy within a report

Use this method when you want to show all issues under a single Initiative that is linked to multiple Epics using a Blocked by or another relationship type.

  1. Set Source type to Issue.

  2. Select the issue that you want to reference in the report.

  3. Check the boxes to include parent and child issues to extend the report.

  4. Click Create.

  5. Follow the steps in the related article to use the relationship link between the Epics and the Initiative to create a custom hierarchy within the report.

You can later change Source type to JQL and use a query to include all Initiatives from one or more projects, as described in this related article.

Troubleshooting

What can you do if the app is missing from the sidebar?

If ‘Pivot Report’ is missing from the top navigation bar, check if it is disabled by following the steps listed in arelated article.

How can you locate the 'Create Report' button if it is missing?

If the ‘Create Report’ button is missing from your tab:

  1. Check whether the ‘Create Calendar’ button appears instead, as shown in the screenshot. If it does, you are currently in the Calendars tab.

  2. Click on the Reports tab to access the ‘Create Report’ button.

Group 325-20260303-030835.png
Can reports be used to display more issues than possible in Jira?

Yes. Reports can display more issues than a board or the Issue Navigator. However, loading time increases as the issue count grows.

Working with high issue count in Cloud

Atlassian notes that searches have no issue limit, but display limits apply:

  • Boards and backlogs show up to 5,000 issues.

  • The Issue Navigator shows only the first 1,000 issues.

A report can help you work around certain Jira limits, though it may increase loading time. For example, a board may fail to load if it reaches the maximum issue limit.

In contrast, you can create a report based on the board or its underlying source filter. However, this report may take longer to load compared to one linked to a board that has not reached the maximum limit.

Working with high issue count in Data Center

The display limit for the Issue Navigator can be increased using a documented workaround. A report does not require this workaround, although very large reports may load more slowly.

Similarly to prior example, a report linked to a board or its underlying source filter may take longer to load if the workaround was applied to increase the limit.

Can you decrease the report’s loading time?

Yes. The number of issues in the report source directly affects Jira’s API performance, which determines the report’s loading time—not Pivot Report itself.

  • To speed up loading, reduce the number of referenced issues or those added through extensions (parent or child issues).

  • Also, specify which projects or boards Jira should search. A narrower search scope means fewer issues for Jira to process, resulting in faster results. Atlassian’s documentation offers additional JQL optimization tips.

In Jira Data Center, alerts help identify slow and complex JQL queries, including those with many custom fields. Atlassian provides detailed thresholds for these alerts in a separate article.

How can you resolve the unbound queries error?
Group 429-20260311-235556.png

The error above appears when the report source is unbound, whether it uses a saved filter or a JQL query. Follow the steps in the related article to resolve it.

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.