How can I create a public dashboard for Jira Service Desk?

[Deleted user]

I was able to give the anyone group project browse permission for the service desk project but got "threatening" errors about needing to reconfigure permissions. Without the permission, I get errors when going to the dashboard url.  The Dashboard and associated filter are both public by the way

[Victor Florin Pana]

Simply ignore the errors if that is what you want to do (make it public) and you understand that by anyone, it means both logged in and not logged in users can view the dashboard but also the all of the issues from your project.

For some reasons, for JIRA Service Desk, as soon as you go out of what Atlassian considers to be the permission standard, you will always get an error notification stating that your project is not correctly configured and there is no way around this.

[Deleted user]

I added the group "anyone" to browse projects and it's letting users open the dashboard.  Oddly, if the user is logged in as a customer (opened the customer portal), the link does not work and keeps returning the user to the portal instead of displaying the dashboard.  When the user logs out, the url will open the dashboard.

This seems like a bug, why can't logged in users (customer portal) see a public dashboard?

[Victor Florin Pana]

Actually it is not a bug. Once a user logs in, he is not anyone anymore he is user X and if user X does is not added to the project or is not a jira group which is added to the project, then he will not see the content. So besides anyone you also need to ensure that logged in users can see the content so you will need to give browse rights to the group that contains all users from your instance.

[Deleted user]

I set up a group and included all users, all logged in users was already added to the browse permissions.  I still get switched to the portal when I try to open the URL for my dashboard.  When I log out I can then open the browser.

[Victor Florin Pana]

Ok, now I understand ... the problem is that you are trying to expose a jira dashboard to service desk customers. The dashboard is a functionality coming from JIRA Core/Software and not related to Service Desk. So a service desk customer will not be able to see it, as he does not have access to that application.

[Deleted user]

Understand but the dashboard in question has been made public and when a jira service desk user is signed in (customer account) they cannot view the public dashboard from jira software.  That's a bug to me.  they have to sign out and then then can view the public dashboard.  Being signed into jira service desk as a customer shouldn't prevent viewing an otherwise public jira software function.

[Seth Manwaring]

That's awesome. Making the dashboard public might share it with everyone in the world except Jira users. This just keeps getting funnier.

[JCameron]

I found my way here in an attempt to get around the breaking changes made by the introduction of the "Customer Service Management" feature. Our external customers are now no longer able to see their company's support ticket history due to how the new "Service Collection Premium" arrangement altered the access checking in the Confluence Jira issue list widget. They no longer register as having "Jira app access". I was able to fix this initially in June 2026 by marking them as "guest" users in Jira and just never assigning them to a Jira project. Apparently that broke sometime close to yesterday (July 7th, 2026) when Atlassian changed how the Confluence widget works. Even though my external users have "browse" permissions in the JSM project and can see the tickets they've filed (or are participants on) under "requests" in the Portal, the query in Confluence now fails.

I thought we might be able to get around this problem by creating a "public dashboard" but have the queries all use "currentUser()" like the Confluence page has. That way "random" people don't see anything populating the dashboard widgets.

Apparently that doesn't work either because of this "intended behavior". As someone above said, "public apparently means everyone but Jira users". It's been a maddening few days trying to fix what they broke and customers of ours had been happily using.