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

[#1]

Hi everyone!

It's been a while since we shared more publicly what we're working on, this article is here to correct that. The truth is we've been crazy busy since JPD became generally available in May 2023. A few months ago we reached an amazing milestone with 10,000 paying customers, and the growth hasn't slowed down one bit since then! 

I remember reading somewhere that before you find product-market fit you need to keep pushing a boulder up the hill (like Sisyphus), but after you found it you end up running after this boulder as it races downhill, trying to keep up desperately. There's definitely some truth to that and many of us on the team can relate 😅

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. 

[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?