---
title: "Jira Product Discovery Pricing: Creators, Not Users | Sleekplan"
canonical_url: "https://sleekplan.com/blog/jira-product-discovery-pricing"
last_updated: "2026-09-23T23:04:33.258Z"
meta:
  description: "Jira Product Discovery bills per creator: $0 for three, then $10 or $25 each per month. Published views are read-only, so customers cannot vote."
  "og:description": "Jira Product Discovery bills per creator: $0 for three, then $10 or $25 each per month. Published views are read-only, so customers cannot vote."
  "og:title": "Jira Product Discovery Pricing: Creators, Not Users | Sleekplan"
---

## How does Jira Product Discovery pricing work?

Jira Product Discovery is billed per creator per month: $0 for up to three creators, $10 per creator on Standard, and $25 per creator on Premium, with Enterprise quoted by sales. Atlassian’s own Jira Product Discovery pricing page carried those three figures when we checked it on 20 September 2026, and it advertises up to 17% off for annual billing. [G2’s listing for Jira Product Discovery](https://www.g2.com/products/jira-product-discovery/reviews) shows the same three plans and the same two prices.

| Plan | List price | Creators | What Atlassian’s page says |
| --- | --- | --- | --- |
| Free | $0 | Up to 3 | “Free forever for 3 creators”, 2 GB of storage and Community Support |
| Standard | $10 per creator / month | Billed per creator | “For individual teams to get started” |
| Premium | $25 per creator / month | Billed per creator | “More visibility and control across teams” |
| Enterprise | Quoted by sales | Billed per creator | “Advanced compliance, scale and security”, billed annually |

One detail in the small print is worth planning around. Atlassian’s pricing page states that if you are on the Free plan and exceed the user limit, the site is automatically moved to a 14-day free trial of the Standard plan. A fourth product manager joining the space is enough to trigger it.

## What is a creator, and who is free?

A creator is a billable Jira Product Discovery user who creates and manages projects, ideas, fields and views, and a contributor is a free user who only needs an Atlassian account. Atlassian’s pricing page states it in those words, and adds the part that matters for budgeting: users are contributors by default if they already have product access to Jira or Jira Service Management.

**Creator**: the licensed seat. Product managers who own the idea backlog, define fields and build views.

**Contributor**: free, unlimited in practical terms, and the default role for anyone who already holds a Jira licence. Contributors comment, add insights and vote inside the space.

So the budget question is not how many people will look at your ideas. It is how many people will own them. For most teams that is the product management group and nobody else, which is why a company of 400 can run Jira Product Discovery on four paid seats.

## Is Jira Product Discovery included with Jira Software?

No, a Jira Software licence does not make someone a Jira Product Discovery creator. It makes them a contributor by default, which is free but read-and-react only. Creators are described on Atlassian’s own pricing page as billable, paid users of Jira Product Discovery specifically, so adding the product adds a new per-creator line to your Atlassian bill rather than absorbing into the seats you already pay for.

## What does a real bill look like?

Four product managers on Standard is $40 a month, and the same four on Premium is $100 a month, before any annual discount or negotiated rate. Nothing in those numbers moves when engineering, support or sales grows, because none of those people need a creator licence.

List price is also not what larger buyers pay. [Vendr’s Atlassian buyer guide](https://www.vendr.com/buyer-guides/atlassian), built on 834 purchases, puts the median annual Atlassian contract at $91,357 and reports buyers saving 11% on average, across a range from $11,705 to $293,246. That figure covers a whole Atlassian estate rather than Jira Product Discovery alone, but it tells you something useful: if you are already a meaningful Atlassian customer, a new per-creator SKU is a negotiation at renewal, not a checkout page.

## Can customers submit and vote on ideas in Jira Product Discovery?

No: a published Jira Product Discovery view is read-only, so customers can see the ideas and the roadmap but cannot add an idea or cast a vote. Atlassian’s frequently asked questions article for the product says a published view can be shared with internal stakeholders, partners, customers and end users, and that the view “is accessible in read-only mode”. Asked directly whether people can comment and vote in a published view, the same article answers “Not yet but it’s on the roadmap”, and points to the workaround: give each person an Atlassian account and add them to your site with the free Contributor role.

![A lit shop window showing a display board inside, with the door beside it bolted shut](https://blogassets.sleekplan.com/bolted-shop-door-as2l232c8wp-w800.webp)

That workaround is fine for twenty colleagues. It does not survive two thousand customers, because every one of them needs an Atlassian account and a place on your site before they can register an opinion. The practical shape of Jira Product Discovery is therefore an internal discovery workspace with a shop window: customers can look through the glass, and the door is bolted.

## Why the read-only limit matters more than the price

A vote count is not a roadmap, and nobody serious argues otherwise. Marty Cagan has spent years making the case that [customers are not the source of true value creation](https://www.svpg.com/customer-inspired-technology-enabled), because they do not know what is technically possible and often do not know what they want until they see it. Teresa Torres frames the same split cleanly in [her history of modern product discovery](https://www.producttalk.org/rise-modern-product-discovery), quoting Cagan’s definition of discovery as figuring out what to build and delivery as then building it.

Both are right, and neither is an argument for collecting nothing. Customer requests are evidence, not instructions. What a public board gives you is the raw material discovery runs on: how many accounts want a thing, which plan tiers they sit on, what they were trying to do when they asked, and who to call when you want a real conversation. Without an open intake, that evidence arrives filtered through whoever shouted in the last sales call.

The gap in Jira Product Discovery is not the $10. It is that the cheapest, highest-volume source of discovery input, your own users, is the one group the product will not let in.

## What a public idea board adds on top

An idea board that customers reach without creating an account closes the gap that a read-only published view leaves open. [Sleekplan’s idea management](https://sleekplan.com/use-cases/idea-management) runs that board as a widget in your app or a standalone site on your own subdomain, with no Atlassian account and no seat on your site required from the person posting. Ideas can also arrive through the API.

Three things about that board change what you get back:

- **Duplicates are caught at the door.** Similar posts are suggested while someone is still typing, so one idea stays one thread with one vote count instead of splitting into six.
- **Votes are weighted by who cast them.** Each idea carries the customer attributes you send, such as plan tier, MRR, account ID and segment, and the impact score combines demand, effort and your own priority. The ranking survives a loud trial user.
- **The board can be private.** It can be public, password protected, restricted to a list of email domains, or gated behind single sign-on with JWT or SAML, so the same product covers a customer board and an internal staff board.

## How the two fit together

Sleekplan sits in front of Jira rather than replacing it, and the integration creates Jira issues, not Jira Product Discovery ideas. From any Sleekplan post you click Push to Jira to create a new Jira issue, choosing the project, issue type and any required fields up front, and existing Jira tickets can be linked to multiple posts so one engineering effort reports back to everyone who asked. When the Jira issue moves to Done, the Sleekplan post moves to Released and everyone who voted gets an email. The [Jira integration page](https://sleekplan.com/integrations/jira) covers the setup, which is a Marketplace install and a field mapping per project.

If you are already doing this work by hand, our walkthrough on [tracking feature requests and bugs with Jira](https://sleekplan.com/blog/keep-track-of-feature-requests-and-feedback-with-jira) shows the same flow step by step.

## Deciding whether to add it

Start by counting creators, not users, and price Jira Product Discovery at $10 or $25 times that number. Three or fewer and it costs nothing today, which makes the Free plan an easy experiment for a single product team.

Then ask the second question separately, because Atlassian’s price list does not answer it: where will customer ideas actually be collected, and what happens to the person who submitted one. If the answer is a read-only link, you have bought a better internal backlog and changed nothing about intake. A public board in front of Jira costs less than most teams expect, and [Sleekplan’s plans](https://sleekplan.com/pricing) start at $0 for a board and changelog, with the Jira integration included from the Starter plan at $13 a month billed yearly.

Mmarco·Sep 20, 2026

More from the Journal

[Product ManagementSep 20, 20267 min Aha Pricing: What Each Product and Tier Costs→](https://sleekplan.com/blog/aha-pricing) [Product ManagementAug 1, 20266 min The New Era of Product Management and How SaaS Teams Can Win→](https://sleekplan.com/blog/the-new-era-of-product-management-and-how-saas-teams-can-win-6992) [Product ManagementJul 25, 20268 min ChatGPT for Product Managers in 2026: Workflows, Guardrails, and Specialized Copilots→](https://sleekplan.com/blog/chatgpt-for-product-managers-in-2026-workflows-guardrails-and-specialized-copilots-9490)

Keep up

## New essays land on LinkedIn every Tuesday.

Follow Sleekplan on LinkedIn — we post every new piece there, plus the shorter notes that never make it to the journal.

[Follow on LinkedIn](https://www.linkedin.com/company/sleekplan/)

Done reading? [Try Sleekplan free ](https://app.sleekplan.com/sign-up/)