The real challenge with collecting Jira Product Discovery (JPD) ideas
Q: Why is collecting ideas in Jira Product Discovery harder than it looks?
Most teams don’t struggle with getting ideas — they struggle with getting usable ideas into JPD. Feedback arrives from Jira Service Management tickets, Slack, emails, sales calls, surveys, and customers who don’t even have Jira access. By the time an idea reaches JPD, it often lacks context, ownership, or impact — which makes scoring and prioritization unreliable.
This guide answers a common Atlassian Community question:
“What are the best ways to collect ideas for Jira Product Discovery — internally, externally, and from support — and how do I actually use them for prioritization?”
Below are four practical, Jira-native ways to collect JPD ideas, with concrete setup tips and best practices.
Q: What is Jira Product Discovery, and what is it used for?
Jira Product Discovery (JPD) is Atlassian's tool for capturing, prioritizing, and managing product ideas before they turn into development work. It gives product teams a single place to collect ideas, attach supporting evidence, score them, and decide what to build next.
The catch is that JPD is designed for internal product teams. The people with some of the most valuable input — customers, support agents, sales, and partners — usually have no direct way to add ideas, and giving everyone a contributor license isn't realistic. That gap is exactly what the four approaches below are built to close.
1. Using Jira Product Discovery’s native idea creation (internal only)
Q: Can users submit ideas directly into Jira Product Discovery?
Yes — Jira Product Discovery allows contributors to create ideas directly inside a JPD project.
How to set it up:
Go to JPD project settings → Ideas
Enable “Allow contributors to create ideas”
Define required idea fields (problem, impact, customer segment)
How to use it well:
Add idea templates to guide contributors
Align fields with scoring criteria (e.g. customer impact, confidence)
Train internal teams on what “good input” looks like
Limitations to be aware of:
Contributors must have Jira access (and count toward licenses around $10 per contributor for standart plan)
No conditional logic or dynamic questions
Not suitable for customers, partners, sales and support teams
Best use case: PMs, engineers, and internal stakeholders already working in Jira.
2. Collecting ideas from Confluence (structured internal feedback)
Q: What form should we use to collect JPD ideas in Confluence?
Jira Product Discovery doesn’t currently provide a native idea form that can be embedded into Confluence pages. You share a link to JPD idea creation, but you can’t control structure, logic, or automatically capture metadata like source or product area.
Because of that, teams usually embed a Smart Form designed for JPD idea intake directly into Confluence pages such as roadmaps, RFCs, discovery docs, or workshop notes.
How teams typically set this up:
Embed a Smart Form on the page where discussion happens
Use structured fields (problem, impact, affected users)
Use hidden fields to map to idea fields like ideas source or discovery stage, to shorten the form:
Source = Confluence
Discovery stage = New
Each submission creates a JPD idea automatically, already tagged and ready for scoring - without requiring contributors to open Jira or have a contributor license.
Best use case: Async feedback, roadmap reviews, and discovery workshops or just a rugular meeting pages where feature idea can apper
For a full step-by-step (including making the page public for people outside your org), see How to Collect External Ideas for Jira Product Discovery Using Forms in Confluence.
3. Using Smart Forms as a unified idea intake layer (all channels)
Q: How can we collect ideas consistently from customers, support, and internal teams?
Many teams use Smart Forms for Jira as a single, standardized intake layer in front of Jira Product Discovery. Instead of having separate entry points for customers, support, and employees, the same idea form can be reused across multiple channels.
Below are the most common and effective ways teams collect ideas with
Auto-attach idea forms to customer requests (Jira Service Management)
Best for: Customer-driven ideas backed by real support cases
Automatically add an Idea / Product Feedback form to selected JSM request types
Customers can submit ideas directly from their request
- You can attach an Idea / Product Feedback form as a second form that appers after the main form
Agents can also submit or enrich the same form internally
- Submissions can create or update a JPD idea
Best practice: Add a simple qualifier like “Is this a product gap?” to avoid creating ideas for every ticket.
Add idea forms to regular Jira work items (Jira / JWM / JSM)
Best for: PMs, engineers, designers, and support teams working in Jira
Attach the idea form to bugs, tasks, or discovery spikes
Submit ideas without leaving the work item context
Form responses can create new JPD ideas and all ideas fields will be mapped
This keeps discovery close to delivery and preserves context.
Submit ideas via shared form link (internal employees)
Best for: Sales, Marketing, Customer Success, Operations
Share a form link via Slack, email, or intranet
No Jira access or contributor license required
Use hidden fields to capture:
This replaces unstructured messages with consistent, actionable input.
Add the idea form as a Jira project shortcut
Best for: Frequent internal submissions
Add the form link to the Jira project sidebar
One-click access from the board
Encourages adoption through visibility
Teams often use this for recurring discovery input like UX issues or improvement ideas.
Share the idea form externally
Best for: Customers, partners, beta users
Share the form via a public link
External users submit ideas without Jira accounts
Each submission can automatically create a JPD idea
- Embed form on your website to collect ideas form website visitors
- Embed form on Conflunce and make the page public.
Key advantage: No Jira contributor licenses required.
Embed the idea form directly in Confluence (Idea Hub pattern)
Best for: Centralized idea collection during discovery, planning, and reviews
Instead of embedding a generic feedback form, teams usually create a dedicated "JPD Idea Intake" Smart Form and embed it across key Confluence pages.
Where teams embed it:
How this improves idea quality:
Contributors submit ideas in context, while reading the document
The form enforces structure (problem, impact, user)
Hidden fields automatically capture:
Source = Confluence
Discovery stage = New
With Smart Forms, each submission:
Creates a JPD idea automatically
Maps fields directly to idea and scoring fields
Lands in JPD ready for review and prioritization
This pattern is often referred to as an internal "Idea Hub" in Confluence.
4. Turning Jira Service Management (JSM) tickets into JPD ideas
Q: How do we move from support tickets to product ideas without noise?
Support teams surface real product gaps — but raw tickets shouldn’t become ideas automatically.
Auto-attach a pre-filled idea form with Jira Automation (new)
Best for: High-signal tickets where you want the customer — not the agent — to shape the idea, in their own words
Sometimes a ticket clearly points to a product gap, and it's better to capture the idea straight from the customer while the context is fresh. Smart Forms' new auto-attach form with values capability lets you drive this entirely through Jira Automation:
- Trigger it on any condition. Use any Jira Automation trigger or rule — priority set to High, a specific request type, an "Is this a product gap?" answer, a recurring-issue label, or an SLA breach — to decide exactly when the idea form should appear on a ticket.
- Attach a form already pre-filled with ticket data. The rule attaches a JPD idea form to the issue with fields already populated from the request (customer, product area, the original request summary), so no one re-types context Jira already holds.
- Let the customer submit it inside the ticket. Set the attached form to external, and the customer can complete and submit it right from their request — turning their own words into a structured JPD idea, with no Jira account or JPD access required.
Because the form is both conditionally attached and pre-filled, you only ask for input when it's genuinely worth capturing — and the idea reaches JPD with real customer context, not an agent's paraphrase.
See the setup in NEW Jira Automation for Forms: Attach the Right Form at the Right Moment.
Another practical JSM → JPD setup:
Best practices when moving from JSM to JPD:
Don’t auto-create ideas for every ticket
Use thresholds (e.g. recurring issue, SLA breach, multiple customers)
Pass context, not just summaries, into JPD
Result:
JPD ideas backed by evidence — not gut feeling.
Turning collected ideas into action (scoring & prioritization)
Q: What happens once ideas are in Jira Product Discovery?
Once ideas land in JPD — regardless of source — high-performing teams:
Score ideas consistently using impact, effort, confidence, and reach
Compare ideas across sources (customers vs support vs internal)
Link ideas to delivery work in Jira Software or JSM
Best practices:
Align intake fields with scoring fields to reduce manual cleanup
Tag ideas at creation (source, segment, urgency)
Review ideas regularly — not just during roadmap planning
The goal isn’t more ideas. It’s clearer prioritization and better product bets.
If you’re exploring how to connect Smart Forms, JSM signals, and Jira Product Discovery into one discovery flow, happy to clarify or share concrete setup examples.
