Enjoying working with the next-gen roadmap, would really like to be able to share it in my org, and with our customers, without needing them to have access to our Jira account.
I'm sure there are business reasons behind this. But it seems like it would be trivial to provide a non-guessable link that has read-only permissions on the roadmap.
Has anyone found the solution for the Jira Roadmap widget giving non-Jira users an error? I'm having two issues similar to this one (Advanced Roadmap and Beta Roadmap in Confluence).
Advanced Roadmap: I've tried doing the Generate Confluence Link in Advanced Roadmap and have set the permissions of Advanced Roadmaps to allow view permissions for Confluence-only users, but my Confluence-only users are still seeing the error.
Beta Roadmaps: We also aren't able to get our Confluence-only users to see the Beta Roadmaps in Confluence. We were using the Next-Gen and it seemed like they were able to view those, but once we switched to Classic we started hearing reports of the widget giving an error.
Thank you for reaching out to Atlassian Community!
Next-gen projects are more simple than Classic ones and one of the features that would maybe allow the roadmap to be public is the "Browse Projects", but since the permissions are not available on next-gen, only internal users have access to the projects and its features.
Currently, there are no feature requests suggesting to make the roadmap public, so please, feel free to raise one on jira.atlassian.com (project JSWCLOUD) adding more details about why this feature is important for your environment.
Hi @Joe Gaudet
You can share a static view of your roadmap by pressing Export in the upper-right corner and exporting an image of it.
You can also visualise a view of your roadmap in Confluence which would avoid the need to login to Jira. Something worth testing here is whether a roadmap in Confluence can be viewed by an anonymous user, thus eliminating the need to login to see it. This isn't something I've personally tested at this stage.
Aside from that, I'd vote on this suggestion, which mentions embedding the roadmap on external pages - JSWCLOUD-17750