📣 A (big) update on Jira Product Discovery pricing, creators and contributors!

[#1]

Update on 04 May: everyone can now use the creator and contributor experience! Open Project Settings > Access to get started. 

👉 Trying the new creator/contributor experiences

👉Trying the feature letting contributors submit ideas

---

Hi everyone,

First off, if this is your first time in the community group: welcome! You can ask for help and discuss product feedback here: Atlassian Community > Jira Product Discovery.

On to the update:

Jira Product Discovery will be graduating from beta to GA (general availability) soon.

We will share more on the next steps for our beta users soon but I wanted to take the opportunity to share an update because I know this is top of mind for many.

Reminder: Jira Product Discovery is moving out of beta and becoming generally available

As we shared earlier: Jira Product Discovery is graduating (and you can see the pricing here).

We will launch a free and standard edition of Jira Product Discovery (JPD).

• The free edition will have up to 3 free Creators and unlimited* Contributors and Stakeholders (I’ll explain these roles in more depth below).

• The standard edition will have unlimited* Creators, Contributors and Stakeholders. Contributors and Stakeholders will be free. Creators will be charged USD$10 per month, with volume discounts as per other Jira products (the more Creators you have, the less you pay per Creator).

As customers of Jira Product Discovery beta, you are currently on the beta edition. At some point you will be prompted to transition to either the free or standard edition. We are sorting through this now and will share more information with you at a later date. Rest assured, your data will not be impacted once the product enters general availability or during your transition from the beta edition to the free or standard edition.

* Note: there is a limit in the number of users you can add to Jira in a site. Whenever we mention “unlimited users” in the rest of this post it should read “unlimited up until you reach the limit of 35k Jira users in the site”.

What changed since the last update?

We have two main updates today:

1. Jira Product Discovery will support 3 kinds of users: Creators, Contributors and Stakeholders.

2. By popular request Contributors will be able to submit ideas - via a customizable form, the Chrome extension, Slack/Teams apps.
   
   

I'm trying to explain it all in this video, or you can read it all below:

Creators, Contributors and Stakeholders

 

Creators (will ship before GA)

Creators can access all features of Jira Product Discovery. These folks are the ones who run the prioritization process, share roadmaps, work on product ideas, and so on.

• Typically: product managers, some designers, some researchers, parts of the engineering team.

• They can do everything in Jira Product Discovery, and are only limited by the permissions they’re granted in each project.

Discovery project, as seen by a Creator:

Contributors (will ship before GA)

Creators invite Contributors to collaborate in Jira. Contributors are people who get a full view on how the roadmap gets prioritized and why:

• Typically the extended product team: all engineers, all designers, all researchers, all product managers

• They can see all the views in the project in Jira but can only perform contributor actions (comment, vote, add insights, add reactions) and submit ideas - if Creators allow it.

Discovery project, as seen by a Contributor:

To better spot the differences - here’s a Discovery project, as seen by a Creator, and in red we highlight what contributors can't do:

Stakeholders (will ship after GA)

Creators can share individual views with Stakeholders, for example the roadmap. Stakeholders can participate in the prioritization process but in a more controlled environment.

• Typically people from leadership, sales, support, customer success, the rest of the company, some customers and partners. Basically people who are not typically in Jira and wouldn’t know how to use it.

• They interact with the view using contributor features (vote, comment, add insights, add reactions) and can submit ideas - if Creators allow it.

• They cannot open the project in Jira, which is really the only difference today between Contributors and Stakeholders. This is for when you want to share a single view only, for example your roadmap. Stakeholders will just be able to see this view, and won’t be able to navigate/browse around your project.

Shared view from a Discovery project, as seen by a Stakeholder:

Contributors and stakeholders will be able to submit ideas

(will ship before GA for contributors, after GA for stakeholders)

By popular request, contributors and stakeholders will be able to submit ideas, using the Jira top navigation bar’s “Create” button and via a configurable idea submission form:

Optionally you will be able to configure the list of fields on the form, as well as select an idea description template to pre-fill the idea description - for example with questions you’d like the requestor to answer (“e.g. what goals does this contribute to?”).

There were quite a few questions about this, so here is a demo that shows how it works and how to use it.

The fine print

What will ship when?

We’re currently actively working on all of this but not everything will ship at once.

Initially, when we launch the free and standard editions:

• Only the Creator and Contributor roles and corresponding experiences will be available.
• The stakeholder role and experience will ship at a later date.

Who can do what?

When we’re done, it will look like that:

	Creator	Contributor	Stakeholder
Free edition	Free, up to 3 Creators	Free, unlimited* users	Free, unlimited* users
Standard edition	$10/Creator/month	Free, unlimited* users	Free, unlimited* users
What they can access
Open a discovery project in Jira	✔️	✔️
Open a shared view	✔️	✔️	✔️
Creator features
Create ideas	✔️
Edit ideas (fields, description, delivery tickets)	✔️
Change the rank/order of ideas	✔️
Create and edit views and sections	✔️
Create and edit fields	✔️
Share views	✔️
Contributor/Stakeholder features
Submit ideas - via a form, Chrome extension, Slack app	✔️	✔️	✔️
Add insights	✔️	✔️	✔️
Add comments	✔️	✔️	✔️
Add reactions	✔️	✔️	✔️
Vote	✔️	✔️	✔️
Administration features
Create projects	✔️
Manage project access and user permissions in a project	✔️
Manage automation rules	✔️

Who can be a Creator?

Any user with product access to Jira Product Discovery on the site (“licensed user”) can be added as a Creator to a Product Discovery project.

From a billing/licensing perspective any user who is given product access to Jira Product Discovery is considered a Creator, whether they’ve been added to a Product Discovery project or not.

There are different ways to give users access to the product on a site: either it needs to be done by a site administrator, or the site administrator can let other users do it as well - you have the same options as for other Jira products as explained here.

Who can be a Contributor?

Any user who has been added to the site can be added as a Contributor on a Product Discovery project, regardless of whether they have access to an Atlassian product or not. That means they don’t even need to have product access to Confluence, Jira Software, Jira Service Management or Jira Work Management. They just need to be in the site’s user base. Free means free 🙂

Who can be a Stakeholder?

Anyone with an Atlassian account, which is free to get at https://id.atlassian.com, regardless of whether they have access to the site or not, can be a Stakeholder.

Next steps

I know the first comment on this post is going to be “when exactly is GA?!” I promise we will share that soon. We will be emailing and posting on the community again shortly. There is no action needed from anyone at this point. As ever, we encourage comments below. As you know, we keep listening to your feedback and it plays a big role in helping us shape the roadmap. Thanks again!

[Nico Seibt]

Hey, thanks for keeping us updated! Do you already know when funcionalities to submit ideas as Contributors, especially via the customizable form, will be available - will they ship with GA or come at a later date, like the Stakeholder role?

[Chris Timms]

Great update @Tanguy Crusson - improvements to contributors capabilities was a key beta request so thanks for taking on the feedback and delivering something!

The new stakeholder view sounds killer, and is exactly what we have been trying to figure out how to surface so this announcement is ideally timed. You have me thinking about public suggestion boards, views for customer steering groups, all sorts of interesting uses!

Regards,

-C

[Tanguy Crusson]

@Nico Seibt great question, I've just clarified that on the post in each section (what ships before or after GA). The ability for contributors to submit ideas via the customizable form will ship before GA.

[Jeny Stoeva]

Hi @Tanguy Crusson ,

Thanks for the update!

Can you please elaborate on what "Submit ideas via a form" exactly means.

[Gail]

Question -- with the JPD automations..... will these have their own execution limits or will they combine with any limits we have in Jira Software or JSM standard plan (500 per month for multi-project or global rules)?      We are very close to our run limit every month right now so we have to watch this very closely as it affects our backup runs.

Thanks

[Tanguy Crusson]

@Jeny Stoeva we're still designing the specifics. But:

1. The blue "create" button on top of the Jira navigation bar will keep working. But we also know it's not great (doesn't show the fields the same way as in JPD, etc.). Eventually we'll add a more specific experience there. 

2. In the meantime We're creating a new button that you can turn on/off to show to contributors: 

You will be able to configure the information that people need to fill in:

This will create the idea in the project, and then creators will need to review it/triage it, etc. if you use an "intake" process.

[Jeny Stoeva]

@Tanguy Crusson

It sounds great! Thank you so much for sharing :)

[Jessica Krogstadt]

Thanks for the updates so excited! I would like to know if we will still have access to the free account with the Enterprise Jira License. Also, Jira admin's seats count towards a creator seat? 

[David Nadri]

@Tanguy Crusson - thank you so much for the update! Great work to you and your team!

Here are some initial questions/feedback. Would greatly appreciate if we can sync up on any of these offline first. 

1. In addition to configuring the fields to display on the Submit an Idea form, can creators configure which fields in the form are required vs optional?
2. What is the best practice for when to add an insight vs a comment on an idea? The articles (What are insights? and Create, edit and manage insights) explain to use insight to capture user needs, but how do Customer Success teams, for example, know whether to add an insight or a comment with this info?
3. What are your thoughts on creating a 'JPD Best Practices' article, including topics such as how to structure & organize your JPD project to support product discovery, common pitfalls to avoid, etc.
4. What are your thoughts on putting together a step-by-step guide on how to take an idea from the discovery phase through the delivery phase using JPD & Jira ("The Journey of an Idea from Discovery to Delivery")?
   
   There is some content already on the pieces of this journey (e.g. Manage the delivery tab), but I think the community would benefit from seeing a real-life example story/use-case/case study of the below diagram end-to-end to understand how JPD fits in the product development process and how it all comes together.
   
   Even better, a guide on how product teams can use Atlassian's products (Atlas, JPD, Jira Software) to view and manage the end-to-end product development process: product mission → product vision → product strategy → strategic initiatives → OKRs → epics → stories. One view that shows how all of these roll up is very powerful. 
   
   If I could book 30 min on your calendar, I'd love to discuss these with you and share some cool ideas with you.

[Jens Schumacher - Released_so]

@Jessica Krogstadt assuming licensing is implemented similar to Jira Service Management, Jira admins won't count towards the license. 

You may refer to this questions for more details.

[Tanguy Crusson]

@David Nadri I've asked @John McKiernan if he could get in touch with you to discuss - right now we're all hands on deck working on the launch but we are planning to do things like what you're suggesting, and John is currently looking into all this. 

[Tanguy Crusson]

@Jessica Krogstadt I see 2 parts to your question:

1. Jira Product Discovery is a different product to Jira Software, and as such it is billed separately. In other words it is not included for free in your Enterprise edition of Jira Software. 
2. It works like Jira Software: site administrators do not need Jira Product Discovery product access (a license) to create projects and manage project settings, but they would need a license to work in the projects. 

[Sufian Siddiqi]

@Tanguy Crusson Thank you! Will it be possible to auto-assign submitted ideas to specific product managers based on the field selection on the form? 

[Tanguy Crusson]

@Sufian Siddiqi Yes you can define an automation rule to do just that (Project Settings > Automation). 

[Jessica Krogstadt]

@Tanguy Crusson thank you so much for the clarification! So we will have access to both the Free version and Standard when GA is launched and can stay Free as long as we stay under 3 creators, is this correct?

Thanks!

[Jessica Krogstadt]

@Tanguy Crusson LOVE the submit idea button idea and template creation!!! This is the answer to my question about how to get ideas in for contributors, looking forward to this!

[John McKiernan]

@David Nadri I love this question/feedback! You have basically described everything on my to-do/in-progress list. Sharing practices and guidance is high priority post GA. We will have webinars, articles, demos, etc. Excited to share more soon.

Would love to chat and hear your ideas. Either book directly here: https://calendly.com/jmckiernan/30min?month=2023-03

Or pop me an email at jmckiernan@atlassian.com (based in Sydney but I start from 7am). 

Chat then

[Bill Sheboy]

Hi @Tanguy Crusson 

Thanks for this information!  Would you please clarify your post above:

It works like Jira Software: site administrators do not need Jira Product Discovery product access (a license) to create projects and manage project settings, but they would need a license to work in the projects. 

Will a Site Admin be able to add/update fields and views without a Creator license?

Thanks again, and kind regards,
Bill

[Neta Ilany]

Hi @Tanguy Crusson any news about when the Jira SW fields will become available on the product discovery project?

This is essential when trying to use the " Create Delivery tickets" option, but also very useful when creating ideas and having the option to use the same attributes from ideation to execution.

When creating Epics, we use some fields on Jira SW, which are not available in "Product discovery". So the "create delivery tickets" action can't be completed. 

The workaround is to create and maintain duplicate fields that have the exact same name and context.

When is this integration planned to take place?

Thanks

[Tomas Bejcek]

Hi @Tanguy Crusson
can you please list the prerequisites for "The standard edition will have unlimited* Creators, Contributors and Stakeholders. Contributors and Stakeholders will be free."
Per the tests one of them is Contributors and Stakeholders have to have at least Jira Work Management licence. Can you please confirm?
Thanks, Tomas

[Boleslaw Nowak]

I'm slightly confused, if you could clarify, the part about Contributors.

quote:

"They can see all the views in the project in Jira but can only perform contributor actions (comment, vote, add insights, add reactions) and submit ideas - if Creators allow it."

but then the screenshot has the create ideas within the red frame that's only available to creators.

As I understand we will be able to configure the board itself to allow submitting ideas by Contributors, right? 

[Tanguy Crusson]

@Tomas Bejcek today, right now, you need a Jira license to be a contributor. That's what we worked on changing over the past month - so when we ship that you'll just need an Atlassian account and be part of the site's user base. (technically speaking, an admin will also need to add you to a specific user group, we'll explain all that in a bit). 

[Tanguy Crusson]

@Boleslaw Nowak I suggest you watch the video that's embedded in the page, it shows how it all works together

[Tanguy Crusson]

@Bill Sheboy site admins without a JPD license will only be able to work in project settings. To work in the project (set up views, fields, create and work with ideas) they'd need a JPD license. 

[Tanguy Crusson]

@Jessica Krogstadt that is correct 👍