What are we up to? Public roadmap for Jira Product Discovery

[#1]

Hi everyone!

We want to thank you all for your trust, and for spending time to give us great feedback. It helps us make this product better every day. We do listen to your feedback - if you want to know more about our process for that you can watch this 30min talk+demo - and it guides our roadmap. 

Today we'd like to share this roadmap with you so you can see what we've been working on and what the product has in store for you in the next few months and beyond. 

---

👉 Jira Product Discovery (JPD) roadmap 👈

And yes, we created it in JPD 🤩

---

We're really excited to be on this journey with you. As usual, let us know if you have any questions! 

PS: if you're new to JPD, make sure to read the Atlassian Product Discovery handbook (PDF version, online version) that explains the ways of working that come with the tool. And if you're on the Premium plan, check out this implementation guide.

[Bill Sheboy]

Hi, @Tanguy Crusson 

Thanks for this information and the team's continuing improvements!

For the "in flight" items which may / could require customer actions, what considerations have been made to add release target timeframes to the roadmap?  For example, if the remaining, unsupported global field types are added for JPD use; improved automation field support (i.e., JPD date fields); etc.

Kind regards,
Bill

[Tanguy Crusson]

Hi @Bill Sheboy - in this roadmap we're just covering the big boulders, not what we call the "rocks" or "pebbles" (continuous improvements) where the things you mentioned would fit. 

FWIW we do plan to continue addressing this (supporting more global fields, date fields improvements, JQL support for those, etc.)

[Stephen_Lugton]

I'm excited for the Team field to be available as we use that all over the place!

[Chris Timms]

Good update @Tanguy Crusson

I am quite disappointed in the focus on the premium tier - specifically for things like hierarchies which are fundamental to product management regardless of your size/complexity as an organisation.

[David Nadri]

I’m disappointed too @Chris Timms - while I understand the business side of things, I agree that certain things - idea hierarchies - are fundamental and should be built into the product. 

[Sebastian Penhouet]

We like JPD but honestly not getting why it's not part of our Jira license we are already paying. We don't want to pay twice.

[Oliver Ward]

@Tanguy Crusson Will "Better insights, feedback and intake" address the problem of having to create an idea before creating an insight? This reverse way of approaching the idea/insight relationship has forced me to subscribe to a different product so that I can collect insights first which I can then derive ideas from. Would love to spend that money on your standard plan instead.

[Tanguy Crusson]

@Oliver Ward yes, that's one of the areas we plan to look at 👍 

[Steven Balduino]

+1 to @Oliver Ward - we're sourcing "insights" from outside of JPD, piping them to JPD so they are enriched with data. The current API is a giant limitation AND so is the point made here: that you require a insights reporter to know which IDEA to tie it too (which they are unlikely to know or get right). So we'd want to dump them as orphaned "Insights" and then later LINK them to the larger idea.

[Matt Hudson]

We have different (configurable) versions of our product for different customers. Will there be a way to enable a view and restrict it to specific users from each Client? - Or do we need to create different Projects, one for each Client?

[Tanguy Crusson]

@Matt Hudson from a project you can publish a view to a set of people (inside or outside your company) and they can only access that view. So you could create view A to give to people P1, P2 and P3; and view B that you give to P3 and P4. 

To open these published views they need an Atlassian account (which is free). 

https://support.atlassian.com/jira-product-discovery/docs/share-project-views/

[John Koehnen]

Hi @Tanguy Crusson - thanks for all that you do here. I have a question for you on a "pebble". I am running an innovation program and want to force all my users to use my defined template for idea creation. This works today on the "Create" button, but users can bypass that with the "Create an idea" button. Any plans to address this?

[Tanguy Crusson]

@John Koehnen yes we'll be unpacking all these use cases as part of this idea 

[Sarin Kanhirapuzha]

Hi @Tanguy Crusson, great work with JPD! This product has some excellent features and workflows. I understand that you can share the roadmap with various internal and external stakeholders. However, it currently lacks an option for external users to suggest new ideas or vote on existing roadmap items. Additionally, it cannot be customised to match our corporate branding. Therefore, we believe that the absence of a customer-facing portal (similar to what Productboard offers) is a significant gap. Is this feature on your roadmap?

[Muhammad Khan]

When is the Roadmaps / cross-project views releasing?

[Mathias Coudert]

@Tanguy Crusson how do you manage backlog? I see only done / now / next? but what aout longer term idea, idea discarded or idea that you still need to assess? 
Also would it be possible to comment or upvote on an idea within the public roadmap? 

[Tom Matthews]

We're loving JPD. One flag from us is that dependency tickets are quite limited at the moment. Unfurling of the tasks nested within an epic is great, but often these are nested in a label, or most frequently a Release/Fix Version for us. Thanks! :) 

[Erki Tammik]

Can anyone share a (webinar) link about the following update: Roadmaps / cross-project views.

[Tanguy Crusson]

Hi @Erki Tammik , see the public roadmap item here (with demo)

[Dan Driscoll]

Hi @"Tanguy Crusson"  What is the JPD strategy to map to Jira Software projects Releases aka FixVersions field?  We use it with a single value to align and target Epics (and child issues) to a Release.  It is desired to visualize and group by this on Roadmap or Timeline view.  Understanding that separate Jira projects have their own Releases values, it's still just a field that we would expect JPD to be able to lift via linked Jiras in an Idea's Delivery tab.  Even if challenging for the multiple values use case, if it could be offered for single value use case, that would be a boon.  If it's already there somehow and I overlooked it, or coming in the JPD Premium roadmap items being tracked, please let me know.    

(editing to try and tag Tanguy, the @ is not really helping me find him)

@Tanguy Crusson Any answer at all would be good.  Just to know you saw this. 

[Ivan Kovalov]

Hey @Tanguy Crusson . Exciting stuff.
Is there a way I can partner up with you folks for Design Partnership on "Insights, feedback and intake"? 
We have started using JPD for roadmap, and I'm currently working out a plan how we can move our insight process to JPD as well from Productboard. Insight processing, intake and closing the loop with customers is the biggest pain point. 

[Mathias Coudert]

> Insight processing, intake and closing the loop with customers is the biggest pain point. 

I second that. 

[Gina Gould]

@Tanguy Crusson this is a small tactical question b/c we are trying to integrate our internal product enablement content in the JPD views like you all do (love that internal content can be explained in the PM workflow btw). When I share a JPD view like you all do for your roadmap how do you automatically get the "about this view" content to automatically appear? It's not doing it by default when we share the view and the "about this view" link is so small people miss it and forget it's there.

Thank You!

(Providing screenshot for reference)

[Kate]

Hi @Tanguy Crusson 

Just wondering if there's a place to submit Feature requests, similar to those for Confluence or Jira? I haven't found one, so I hope you don't mind me dropping this suggestion here.

I'm hoping to submit a feature so the JPD team might look at the ability to lock down certain views 

We've found a couple of examples for this, re: we have a team who have a view for their meeting to check their metrics and view all the work in a list. They don't mind users seeing the information in the tickets, but perhaps would prefer that they weren't able to view them side by side in this breakdown view. Moving these users to the new Stakeholder role wouldn't work as we still want them to submit ideas, so we're kinda caught.

It would also be useful for those of us who end up creating a particular view just to enable the Create Idea form.

[Matt Hudson]

Hi @Tanguy Crusson I have published a view to a User who is only part of one group and yet they can still see all of the other views available, despite those other views being restricted. I have read the "Publishing Views" page several times but I cannot fathom what is going wrong.

Is there anywhere I can get some help for this? - Thanks so much in advance!