Permissions

You can grant selected users access to your reports from the Manage Pivot Reports page, shown in the above screenshot, or from within the report by editing the sharing settings.

This allows selected users to collaborate with you on modifying the report. They can not only view the report contents but also make changes, such as adding custom slices or extending the report source.

When a report uses the same source as a board (such as a JQL filter or space), it reflects changes made to that source, including status updates, sprint closures, or other board configuration changes.

By adding a shortcut, as shown in the screenshot above, you can access the report directly from the board, as described in a related article.

You can use the Manage saved Pivot reports page to:

• Find any created or archived report, regardless of whether it is private, public, or limited to specific users or groups.

• Transfer report ownership from one user to another, such as when the original owner becomes inactive in Jira.

• Change who can access a report, archive or unarchive reports, and delete reports that are no longer in use.

You can perform these actions individually or in bulk by selecting a single report, multiple reports, or all reports, as described in the related article.

You can grant users access to embed a report within a Confluence page, which allows them to:

• Display the default or custom hierarchy of Jira work items, along with their associated worklogs and comments.

• Filter data using Slices and visualize it using Charts.

• Preview the feasibility of assigned work items and due dates using Capacity.

• Identify potential work items in the report using Warnings.

Users can perform these actions only if they already have permission to open both the report and its source in Jira. To learn how to embed a report, refer to the related article.

You can grant users access to widgets, which allows them to:

• Access progress indicators directly from the Work item View in Jira Cloud using the Work item Progress widget, as shown in the screenshot above.

• Display the complete work item tree without navigating to lower levels of the hierarchy, such as subtasks, by using the Work item Tree widget.

• Display report columns and their values for each level of the hierarchy, such as Time in To Do or Time in Progress, by using the Work item Tree widget.

You can grant users access to create reports directly from the Work item View. This allows them to select a parent work item and create a report for the entire hierarchy beneath it.

You can grant selected users access to public reports from the Manage Pivot Reports page, shown in the above screenshot.

By limiting which users or groups can access public reports, you can ensure that external users, such as clients or partners, only see private and limited reports for which they are report owners, report admins, or authorized users.

The example above shows a user with access to their own worklogs and those of their team. You can grant users access to view their own worklogs when they are individual contributors, or access to all worklogs when they collaborate in groups, such as paired programming teams.

This allows users to identify when estimates are exceeded and determine whether assistance is needed to re-evaluate the remaining work.

The example above shows a user with access to their own worklogs and those of their team. Team members may be working from different time zones.

You can allow users to view all worklogs based on Jira’s default time zone instead of their own, ensuring that all users see the same values.

The app’s space-level settings allow a Space admin or Jira admin to:

• On Cloud, enable or disable the Pivot Report tab in the space navigation, which users can use to view the list of reports.

• On Cloud and Data Center, enable or disable the Pivot Report button in the work item view for one or all work types, which users can use to create reports.

• On Cloud, enable or disable widgets in the work item view for one or all work types, which users can use to view progress indicators or the work item tree and create reports.

The app’s space-level settings affect how the app is used within a specific space.

In comparison, the app’s global-level settings affect how the app is used across the entire Jira instance. These settings are listed in a related article.

You can learn more about the differences between a report admin, space admin, and Jira admin in the related article.

Yes. The above screenshot shows a work item in a space where the Pivot Report button is enabled.

For example, when creating a report from the Manage Pivot Reports page, you can select any work item or space that you can access in Jira, regardless of whether Pivot Report is enabled for that work item or space.

Similarly, you can use the Issue Navigator or a saved filter to reference any accessible work item or space when creating a report.

Yes.

A Jira admin can disable the app for one or more spaces while keeping it available in all other spaces. Alternatively, the app can be enabled only for selected spaces and unavailable in all others.

To define which spaces can use the app’s features, follow these steps:

1. Open the Settings menu in Jira's top navigation bar by clicking the gear icon.

2. Select Marketplace apps.

3. Under Pivot Report, click Settings.

4. On the Pivot Report Settings page, select the Integration tab.

5. In the Project Level Integration section, choose Whitelist mode or Blacklist mode.

• Whitelist mode enables the app's features only for the spaces listed in the Projects field.

• In comparison, Blacklist mode disables the app's features only for the spaces listed in the Projects field. All newly created spaces have the app's features enabled until they are added to the Projects field.

To make the app's features available for all spaces, leave the Projects field empty regardless of the selected mode.

Yes. If Pivot Reports is missing from the Apps list, your access to the app was removed, even if you previously were a report owner or report admin and even if have space admin permissions.

By default, after the app is installed, it is visible to all users and groups in your Jira instance. However, access can be restricted to specific users or groups.

Yes. Any user or group can lose admin permissions for a report or lose access if the report is changed from Public to Private or Limited.

For example, a report owner or report admin can remove another report admin using the Sharing Settings pop-up. However, report admins cannot transfer report ownership to another user. Only a Jira admin can perform this action.

Similarly, users who previously had access to a Public or Limited report can lose access if their user account or group is removed from the report's access list, or if the report's sharing level is changed to Private.

No. A signed-out user cannot access an embedded report.

Colined protects your data by not storing it on its servers and by blocking access to the app for signed-out users.

If you are signed out of Jira, you cannot edit reports or use the app’s features, such as the report or calendar list. You can only access exported reports, including Excel files, HTML snapshots, and PDFs.

You also cannot view embedded reports. Even if a Confluence space allows anonymous access, embedded reports display an error message until you sign in to Jira.

How can you tell if you’re logged out of Jira?

You can tell if you’re logged out of Jira by checking whether:

1. An arrow pointing right is shown the top navigation bar.

2. Spaces, Filters, or Dashboards load as blank pages.

These signs indicate your account is signed out.

Can you account be logged out due to inactivity?

Yes. Your organization may set an idle session duration, which logs you out automatically after a period of inactivity, as explained in a related Atlassian article.

Also, check your browser’s site data settings, since closing the browser often signs users out.

Will Jira notify you before logging you out?

By default, Jira does not show a warning before ending your session. To change this behavior, see the related Atlassian article.

Yes. The error message above appears when the report source points to a board that a user no longer has permission to access.

If another error appears in the report, refer to the related article.

Yes. The error message above appears when the report source points to a source that a user no longer has permission to access.

The screenshot above shows the Pivot Report tab appearing in the board navigation, which allows you to display a list of reports within a tab.

Yes. Multiple report admins can edit a report at the same time.

For example, if another report admin or the report owner saves changes while you are editing the report, your unsaved changes may be overwritten.