Using the Issue Navigator

When you create a report using the Issue Navigator, the Pivot Report Options pop-up appears. It allows you to extend the report to include parent and child issues. For more details on these relationships, refer to the related Atlassian article.

Parent issue options

• Extend with parent issues: Enable this option to include the parent of each issue in the Issue Navigator results. For example, if your results include Stories, this option adds their parent Epics to the report.

• Add sibling issues as well: Enable this option to include issues that share the same parent. For example, if your results include Stories, this adds other issues under the same Epics, such as additional stories and their sub-tasks.

• Use sibling issues in estimates only: Enable this option to include sibling values in rollup fields without adding the issues to the report. Rollup fields—such as ∑ Original Estimate, ∑ Time Spent, and ∑ Remaining Estimate—will include values from sibling issues. For example, Epic-level totals will include estimates from all related issues.

Child issue options

• Extend with child issues: Enable this option to include child issues for each item in the Issue Navigator results. For example, if your results include Stories, this adds their sub-tasks to the report.

• Use child issues in estimates only: Enable this option to include child issues values in rollup fields without adding the issuesto the report. For example, Story-level totals will include estimates from sub-tasks.

If you need to further filter the extended contents or change the report source, follow the steps in the related article.

By default, when you create a report in the Issue Navigator:

1. Report name – If you use a saved filter, the report’s name matches the filter name. If you use an unsaved search query, the report is named Custom Search. Until the report is saved, its name remains a hyperlink to the search query in the Issue Navigator.

2. Description – The report description shows whether Parent, Sibling, and Child issues are included, based on the selections in the ‘Pivot Report Options’ pop-up.

3. Tabs included – All tabs are available by default: Issue Structure, Pivot, Charts, Worklogs/Comments, Capacity, and Warnings.

Yes. You can test the Pivot Report app button in Jira’s Issue Navigator using sample search results. This works for both unsaved searches and saved filters on the demo site.

Yes. You can share the URL of an unsaved search query or share a saved filter.

A saved filter can also be emailed by clicking the ‘Share’ button in the Issue Navigator, as documented by Atlassian for both Cloud and Data Center.

Yes. You can prevent users from creating reports from the Issue Navigator by removing their access to the app entirely. To revoke or restore access, follow the steps described in the separate article.

Yes. You can extend the report to include issues linked through relationships such as Blocked by or other link types. However, these issues can only be added by modifying the report source after the report has been created.

Refer to the related article for steps on how to include them.

If the Pivot Report button is missing from the Issue Navigator, check if it is disabled by following the steps listed in a related article.

In the Issue Navigator, you can switch between Basic and Advanced (JQL) search modes.

If Basic mode is selected, click JQL to switch to Advanced mode.
If Advanced (JQL) mode is selected, click Basic to switch back.

On Data Center, the Basic option appears only when ‘JQL’ is selected. On Cloud, both options are visible at all times.

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.

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.

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.