Atlassian Team members are employees working across the company in a wide variety of roles.
August 19, 2021 edited
@Dave Hennessy@Lukas Karrer we had to fix something re: product analytics for this feature, which means that I'll probably give you access tomorrow. Stay tuned!
I was trying to test creating a public view, but I don't seem to have the toggle to set the page to public. I'm just seeing an alert displaying the current privacy settings for the project itself.
Was this feature removed or does it need to be enabled somewhere else?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 28, 2022 edited
Hi @Josh we have since retired this feature as adoption was very low and it carried substantial technical risks. We're currently re-thinking how we can help product managers share their plans with other people.
First, to share roadmaps for our software development team internally with other staff members who don't have Jira licenses about what is being worked on at the moment.
Second, to share roadmaps for our software development team externally with our customers about our upcoming releases.
Ideally, it'd be able to integrate with JSM to allow feature requests to be created from that roadmap, but our main hurdle right now is sharing roadmap information with non-Jira Staff and Customers.
You can actually share internally with staff members by adding them to the Jira Product Discovery product (and not the other Jira products in your site), and since JPD is free during beta that won't impact your bill. You can also embed a view in a Confluence page (if you copy and paste a link to a view in a Confluence page it will show that view as embedded on the page if people have access to it)
We don't have a solution today to share the roadmap with customers today yet though.
Use Case: We have several internal teams which care about specific projects (i.e. marketing cares about their marketing projects on the roadmap). We've created a view for them to show our roadmap that highlights their projects. The marketing team are not Jira users so we can add them to JPD while it's free. When it's not free, there may be a discussion which leads to questioning JPD price and who has access.
How I've seen other systems handle this:
Have free accounts for a certain role type (i.e. viewer, contributor, etc.) - ProductBoard
Have a URL and web version that's publically available but can be optionally password protected - Roadmunk (my personal favourite option for sharing - see image below)
There are a wide range of solutions used internally at Atlassian. For Jira Product Discovery we use the following today to manage user feedback:
This community group + the Chrome extension, for example this is what I just did with your feedback :)
An in-app widget + a Jira Service Management queue for inbound feedback we receive in-app:
Dovetail + the Chrome extension to capture learnings from user interviews
And all of this gets tagged to ideas in Jira Product Discovery
To be honest a few of us still have PTSD from our days working on Hipchat and using UserVoice to crowd source user feedback, so we're thinking through how to best tackle the feedback collection/management problem area.
Disappointed to see this was abandoned, public roadmap viewing is a deal breaker for us given this feature is currently available via our existing tools (product board) as much as it would be great to switch this will prevent any further progress on that plan.
Having the ability to share the roadmap with non JIRA and confluence users within the organisation would be something we would be very keen to see as well.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Hello, I discovered the public sharing feature was removed (low adoption, technical concerns). In my case, I'd first search for a public sharing over a logged-in sharing (requiring a jira account). Mainly because the challenge about sharing and engage around a roadmap is more with people outside the team than the team itself (who is +/- daily aware of what's going on).
Considering tools:
- People from the team? They may already have a Jira account (JPD strength is its native Jira integration), I just need to give them a View access, easy. - People not in the team (other teams, sponsors, customers) ? Few'd have a Jira account and the "Oh no, yet another tool ..." situation is real. It is not only a financial concern (when JPD leaves beta), but most of all an adoption topic (habits are hard to change).
I consider JPD as a way to share an information directly from this "source of truth", without extra-effort to make this information accessible, while viewers can have a simple interaction (vote, comment) within the tool. Exporting a PNG of the roadmap makes it quickly outdated, and any interaction will be stored outside JPD (Isn't it the aim of JPD to centralise data ?).
Echoing the above sentiments, we would love a organisation (internally public) facing roadmap, or even the ability to embed the roadmap onto our intranet sharepoint. Our team services a large number of non-tech internal customers (eg payroll, finance, marketing etc) as we deliver process improvements and CI initiatives for their teams. It would be great for them to be able to see where their idea is currently up to, what others may be already submitted (to prevent duplication) and what priority has been assigned. We want to be as open with our internal customers across the organisation about where our team is dedicating our resources.
There isn't a need for them to have a jira licence assigned and this would be overkill for the majority of users. We know that while JPD is free during beta there would be a massive bill that occurs when it transitions to a paid licencing model if we just added all users in bulk. Thanks!
Really a letdown to know this feature was abandoned since it's the go-to feature for most competitors in this area (Productboard and Airfocus). I Hope Atlassian will rethink this since sharing this kind of content with internal users doesn't seem so useful to me (there are plenty of ways in Jira to gather feedback from internal users).
56 comments