Public Dashboard and Filter Warnings in Jira Pre-Flight Checks
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This documentation offers guidance on how to restrict access to dashboards and filters on the Jira server, effectively preventing Jira pre-flight check warnings.
Solution
Overview
Jira pre-flight checks issue warnings if dashboards and filters are shared with the public. After migration to the cloud, this allows anyone with the URL to see the names of dashboards, dashboard gadgets, and filters and potentially access openly-shared issues within them.
Although it is not a blocking pre-flight check, it's strongly recommended to restrict dashboards and filters to "Logged in only users".
This recommendation is also included as a step on the Jira pre-migration checklist.
A singnificant effort is needed for manual review and permission updates. This document outlines steps for updating permissions by modifying relevant records in the Jira database.
Also, this article is a workaround for JRASERVER-65027 - Options to automatically make all Public filters and dashboards to Logged-in users
Update permissions for dashboards and filters
Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
To modify the share permissions for dashboards, dashboard gadgets, and filters, run:
1 2 3 4UPDATE sharepermissions SET sharetype = 'loggedin' WHERE sharetype = 'global' AND NOT (entityid = 10000 and entitytype = 'PortalPage');In the previous query, the exclusion of the System Dashboard was due to incomplete testing of its public visibility. As a result, we included entityid = 10000 and entitytype = 'PortalPage' . Furthermore, there is an existing feature request addressing this limitation which is JRASERVER-64165 - Administrators should have the ability to restrict access to the System dashboard
To verify that the above query is executed successfully, run the following query:
1 2 3 4SELECT * FROM sharepermissions WHERE sharetype = 'global' AND NOT (entityid = 10000 and entitytype = 'PortalPage');Once the update query has been executed, reindex Jira to ensure that the values are correctly updated when later viewing and checking permissions in a browser.
Was this helpful?