Jira Product Discovery pricing and the total cost of Jira + JPD
What does Jira Product Discovery really cost after Jira seats, creators and cross-product administration are included? Current JPD pricing, scenarios and when the Atlassian stack beats one connected Product OS.
Key takeaways
- JPD bills creators; contributors are free but have narrower permissions.
- On the public monthly list price, Standard is $10 and Premium $25 per creator; Free supports three creators.
- The JPD invoice is not the full cost when a team also pays for Jira and maintains boundaries between strategy, discovery and delivery.
- Jira + JPD remains stronger when the Atlassian ecosystem matters more than one shared operating model.
The short answer: Jira Product Discovery bills creators, not everyone who views or comments on an idea. As of August 27, 2026, Atlassian’s public monthly list price is Free for up to three creators, $10 per creator for Standard and $25 per creator for Premium. Contributors are free.
That answers “how much does JPD cost?” but not yet “what does our product operating model cost?” A team usually pays for Jira too, perhaps Confluence and Marketplace apps, plus the work required to keep goals, evidence, ideas and tickets consistently connected.
Check current plans on the official Jira Product Discovery pricing page. Pricing and packaging can change, so every cost table needs a checked date.
JPD creators and contributors are different roles
A creator creates and manages discovery projects, ideas, fields and views. This is the paid role. A contributor can participate with narrower permissions and is free. Atlassian also states that users with Jira or Jira Service Management product access become contributors by default when they have access to JPD.
Headcount is therefore the wrong input for a cost model. Count:
- who actually edits ideas, fields, prioritization and views;
- who only adds a comment, reaction or insight;
- who needs a Jira seat for delivery;
- who only reads a roadmap or decision outcome.
One bad estimate makes every stakeholder a creator “just in case.” The opposite error creates too few creators and turns one person into the discovery administrator for the entire team.
JPD cost for 3, 5, 10 and 25 creators
The table uses public monthly list prices. It excludes Jira licenses, tax, annual discounts and negotiated Enterprise pricing.
| Creators | Free | Standard at $10 | Premium at $25 |
|---|---|---|---|
| 3 | $0 | $30/month | $75/month |
| 5 | unavailable | $50/month | $125/month |
| 10 | unavailable | $100/month | $250/month |
| 25 | unavailable | $250/month | $625/month |
This arithmetic is useful but incomplete. If the same ten people deliver work in Jira, Jira is billed separately. If goals live in another product, that product belongs in the model too. Only then do you have the total stack cost, rather than one line on an invoice.
What the Jira + JPD stack does well
Jira remains a deep, proven system for engineering execution: workflows, permissions, automation, Marketplace apps and reporting. JPD adds a space for ideas, prioritization and views with a native connection to Jira work items. A team already operating in Atlassian gets familiar identity, administration and a natural bridge to delivery.
Choose Jira + JPD when:
- engineering depends on deeply customized Jira workflows;
- the organization already standardizes access through Atlassian administration;
- Jira Marketplace apps run critical processes;
- product discovery should sit close to Jira delivery but does not need to share one model with OKRs and research.
That is not a weak compromise. It is a rational architecture for many organizations.
Where the hidden boundary cost appears
The problem starts when the goal lives in one system, an interview in a document, an insight in JPD and the work item in Jira. Every boundary needs an agreement:
- which relationship is mandatory;
- who maintains it;
- what happens when priority changes;
- where the evidence behind a decision can be read;
- how a stakeholder sees what shipped and which outcome moved.
An integration can copy an ID and status. It cannot guarantee that a team preserves the meaning of the relationship. Administrative cost is not only time spent. It is the chance that a decision can no longer be reconstructed later.
One Product OS: what you gain and give up
WorkThroughLine models goals, OKRs, interviews, insights, opportunities, solutions, experiments, work items and sprints in the same domain. Its trace graph follows linked work from evidence into delivery. Stakeholders and guests do not consume maker seats; the published Team plan is 17,900 RSD/month for up to 10 makers and Growth is 34,900 RSD for up to 30. Everything is free during early access.
Price is not the only distinction. One model means fewer synchronization rules and fewer places where context can disappear. But WorkThroughLine does not currently match Jira’s workflow depth, integration count or enterprise maturity. When those are essential, Jira + JPD is the better choice.
What moving from JPD looks like
The WorkThroughLine Jira Migration Assistant can connect Jira Cloud directly or accept a CSV. Preflight first shows projects, types, users, JPD entities, relationships and warnings without writing data.
JPD ideas and opportunities map to opportunities; interviews and insights keep their discovery role when available in the source data. Jira issues become work items, and stable source identities prevent duplicate records during a repeated import.
Do not assume every configuration moves automatically. Custom-field semantics, automation, Marketplace data, specialized views and permission rules need an inventory and a manual decision.
Read the detailed WorkThroughLine vs Jira comparison, open the migration guide, or use the controlled-cutover checklist.
The decision in one table
| Need | Likely better fit |
|---|---|
| Deep engineering workflows and Marketplace apps | Jira + JPD |
| Atlassian identity and administration are already standard | Jira + JPD |
| Goals, discovery and delivery in one model | WorkThroughLine |
| Small product team without dedicated Product Ops administration | WorkThroughLine |
| Enterprise governance and a broad integration ecosystem | Jira + JPD |
| Direct traceability from evidence to work item | WorkThroughLine |
Do not choose from the lowest line-item price. Count paid roles, products and the boundaries someone will maintain for the next two years.
Frequently asked questions
How much does Jira Product Discovery cost?
As of August 27, 2026, the public monthly list price is Free for up to three creators, $10 per creator for Standard and $25 per creator for Premium. Enterprise requires contacting sales. Check Atlassian's pricing page before purchasing.
Are JPD contributors billed?
No. Creators are paid users who create and manage projects, ideas, fields and views. Contributors are free and can participate with narrower permissions.
Is a Jira license included in the JPD price?
Do not treat the JPD price as the complete Jira bill. Jira and JPD have separate plans and roles, so a cost scenario must include both products and the actual number of paid users.
Can WorkThroughLine import JPD data?
Yes. A direct Jira Cloud connection or CSV preflight recognizes JPD context and shows mappings before writes. Custom configurations and app-owned data still require manual review.