Some of our customers have requested that our Jira apps be made available in Jira Product Discovery. We would greatly appreciate it if support for third-party apps were introduced in Jira Product Discovery.
We were looking into few options for our SAAS model products and their roadmaps. The teams prefer to keep the JPD project/workspace set as private in case of any Tenant specific roadmap items. A majority of the roadmap items would be universal to all tenants however we were requested to maintain some confidentiality with certain tenant specific roadmap items. Hence, we made the JPD project private, filtered on tenant specific tags and created public-facing Views/published Views per tenant. Since these tenant specific roadmaps are now in 4 different JPD projects/workspaces (could be in more projects later), we didn't see or find a way to consolidate roadmaps across multiple projects and create a public facing View. We can use Roadmaps/Plans space and used a filter to get one list of roadmap items from multiple JPD projects however did not see an option to create a public-facing View from there. Is there any other way or future option to allow published Views from Roadmap/Plan space?
Atlassian Team members are employees working across the company in a wide variety of roles.
September 29, 2025 edited
Hi @Shalini Devi - the team's currently working on supporting publishing views from Roadmaps.
Question: what do you mean by "public facing view"? Did you want to publish it so that anyone on the internet can access the view without logging in (anonymous access), or just people from your company or people you add via email address? Thanks.
@Tanguy Crusson I was thinking people you add via email address. If we made the JPD project private then I don't think we want Tenant A to see some specific features that Tenant B asked for. For example, if we create these selective roadmap View for Tenant B and made this public, as in without logging, then Tenant A or any others will be able to see it anyway. If we made it visible to people in your/our company, then it may not work if Tenant A is the business side people in your/our company itself. Tech, Product and select reps would be working for all Tenants. Tenants may be in house business side or externals tenants when we have a SAAS model.
Atlassian Team members are employees working across the company in a wide variety of roles.
September 29, 2025 edited
@Shalini Devi perfect. We're actually not going to support public views (anonymous access) for publishing views from Roadmaps for exactly that reason: figuring out what data to show / permissions is way too tricky
@Tanguy Crusson Thank you. Indeed, permissions can be tricky. I was thinking if we used some sort of Group option and provided access to cross-project Views to select Groups. I know JSM has/had some sort of Group concepts and access by Groups. If something like that was possible then we could set up Groups for each Tenant and provided access to Group. I haven't explored the Teams side yet in case that is similar setup.
Could you please consider adding functionality that allows us to include specific Jira groups in the default project permissions when a Jira Product Discovery project is created?
At our company, we have an automated invoicing system that regularly checks all Jira projects. If the system doesn’t have access to a project (it uses the administrator group), then triggers numerous error messages and alerts for our teams.
We know this functionality is available for Jira Software projects, but it currently doesn’t exist for Jira Product Discovery. Having the ability to automatically assign default groups to new Product Discovery projects would help us avoid these access issues and reduce unnecessary alerts.
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 Champions.
Would really appreciate some longer field types be worked into JPD. The reason I request this is because I would like to port over some technical complexity description and testing description fields into at least the JPD work item view. That way those descriptions can be globally accessed from JSM, Jira or JPD. (We currently support both operations items and new features. We are capturing requests via JSM and then I have a Grooming Form where I can capture the technical complexity description and testing descriptions so we have an idea of what will be involved with it. We do our initial triage in JSM, then from there if it is an incident or support item --> a ticket inside our Incident and Support Kanban project is created. However, if it is a longer term project request, after I do the initial triage, I then trigger automation to create an idea for the item in our JPD for further grooming. After more robust grooming is done, then the JPD ticket will trigger a delivery ticket to be made in our Scrum project.
It would be nice if I can port over the Technical Complexity Description, Testing Description, and Workaround Description fields from my initial JSM triage Form to go all the way through to both JPD and Jira. I would require that these three custom fields have paragraph supported in JPD.
I hope this makes sense. Anyway, I would very much appreciate that longer option in JPD.
When can we get company-managed JPD projects?! Its VERY painful rolling out standardized JPD projects across an enterprise without company managed projects.
JPD is not enterprise ready and should be considered a BETA product.
Noticed Atlassian removed JPD from jira.atlassian.com and I can no longer see previous open work items. This shows you don't want to listen to your customers.
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 Champions.
First thing, I am just another Jira customer and have no specific knowledge of what the Atlassian teams are doing. With that out of the way...
None of the Jira Product Discovery (JPD) suggestions and defects have been in JAC as a public-viewable project since JPD was released; it was not removed from JAC. Such JPD-related items may occasionally be mentioned in other projects' items, such as for Jira Cloud. Instead, the only feedback mechanisms are:
occasional prompts from the team to meet with product managers
In my experience, the fastest response from the team for questions / suggestions is this community Q&A group as they actively check new items (and less so for older threads like this one):
Hi @Tanguy Crusson Loving the premium capabilities, any timeframe for when the visualisation of the opportunity tree might be available. it will really help our stakeholders and senior leaders understand the ladder up of initiatives.
As others have already mentioned, it would be great to have a dedicated section for feature requests. That way, you can identify what’s really holding things back, and we’ll know that you’re aware of the issue.
It would also be great if you could update the status fields in your roadmap. My client and I are eagerly waiting to see when you’ll make progress on the hierarchy feature. Right now, though, it’s hard to tell.
65 comments