Problem
Shared dashboards may show no data or empty widgets for some users, load slowly or time out, and have CSV or image exports that are unavailable, delayed, or incorrectly rendered.
Solution
Scenario: Portal charts show no data
In this case, there may be no problem with the chart itself. Jira Service Management portal dashboards only show issues that the portal viewer is permitted to see. A viewer generally needs to be the reporter or a request participant, or the issue must match the selected organization; project and issue security restrictions also apply. A chart can therefore show data for an internal user but show “No data” for a portal customer if none of the filtered issues are visible to that customer.
Test with a known-visible issue that matches the gadget’s filter and project, is associated with the intended organization, and is visible to the customer in the standard portal. Then try a chart filtered to that issue. Leaving Organization and Portal user blank in the Shared Dashboard access restrictions makes the dashboard available to all customers of the selected Jira Service Management project; filling either field narrows the audience. These settings do not override issue visibility restrictions.
Scenario: Dashboard widgets are empty only on remote networks
If Custom Charts widgets work in the office but appear empty for remote users, the remote network may be blocking the content delivery network domain used to serve the widgets. Have an affected user capture a browser HAR file and console log while reproducing the issue. The network administrator can then check whether *.cdn.prod.atlassian-dev.net is allowed by the user’s home network, VPN, or security software.
Scenario: Dashboard gadgets time out or load slowly
Large filters can take a long time to process, especially when charts approach the 100,000-issue limit. Where practical, reduce the amount of data per chart by splitting charts across projects, teams, or time periods, or by narrowing the filter to relevant issues. If users still need the full detail set, use an Issue List for that detail and charts for a smaller, aggregated dataset. If a small result set is still unusually slow, the delay may be in Jira’s response to the specific query; provide the gadget configurations, a HAR file, and a browser console log captured during the slow load so support can investigate.
Scenario: CSV export is missing or delayed
A Shared Dashboard does not have a single CSV export because it contains multiple gadgets rather than one tabular dataset. Export CSV from an individual Issue List or Custom Charts gadget instead. Large Issue Lists may take longer to generate and download; a large-list export has been reported to complete after a delay.
Scenario: Shared Dashboard image export overlaps gadgets
Image exports may show gadgets overlapping when browser zoom is below 100%. Set browser zoom to 100% and export again. A fix for this behavior was released, and exports were confirmed to render without overlapping after the fix.