JSM comparison
Jira Product Discovery vs JSM Customer Feedback
Choose where to collect customer demand: JSM request voting, Jira Product Discovery ideas, or both. Compare workflows, access and practical handoffs.
In short
JSM customer voting and Jira Product Discovery answer different decisions. Compare demand on an existing service request with idea discovery and roadmapping.
In this guide
Use Jira Service Management customer voting when customers should express demand on an existing service request. Use Jira Product Discovery when a product team needs to assess ideas, weigh tradeoffs and maintain roadmaps. They can work together: request-level demand and idea-level product decisions do not need to live in the same interface.
The useful question is where each decision belongs, not which product can claim “customer feedback.” Jira Product Discovery can already use feedback collected through JSM. This guide explains that native path and where a JSM voting app such as Wezy serves a different need.
Disclosure: We build Wezy. This is a workflow comparison using our product guide and Atlassian’s documentation, checked on 23 October 2026. It is not a benchmark of product effectiveness.
Compare the object and the audience first
| Decision | JSM request with Wezy | Jira Product Discovery |
|---|---|---|
| Main object | An existing, enrolled JSM request | A product idea |
| Typical activity | A signed-in portal customer supports or withdraws support | A product team assesses ideas and prioritization criteria |
| Demand context | Customer votes, represented organizations and recent demand | Insights, fields, votes and other discovery evidence |
| Output | A signal for the team’s request review | Product priorities, roadmaps and links to delivery |
| Access question | Can this customer already access this request? | What can this stakeholder access and do in this discovery space or shared view? |
Atlassian describes JPD as a system for capturing ideas and insights, applying prioritization frameworks and connecting decisions to Jira delivery. Its fields reference includes vote fields, insights and custom formulas. Do not dismiss those capabilities simply because your intake starts in a service portal.
What native JSM-to-JPD intake already does
Atlassian documents an Automation workflow for creating ideas from the JSM portal. A new service request of a specified work type, such as “New Feature,” triggers creation of an Idea in a discovery space, with selected fields mapped across.
That can be appropriate when each eligible incoming request should enter product triage. It also creates an operating decision: who checks whether the idea already exists? A rule that creates an idea is not, by itself, a policy for consolidating repeated requests or deciding what deserves investment.
There is a second documented path: add a JSM request as an insight on an existing idea, using the Chrome extension. This supports a team that wants several service interactions to become evidence for one product opportunity.
Neither path should be described as incapable of collecting customer feedback. Both should be tested against the actual intake process, required access and ownership of the product backlog.
Where customer voting on the request helps
Consider an explicitly hypothetical example. Several customers want a new export option. Support already has a suitable request that customers can access under the project’s sharing rules. The team wants those customers to support that request without creating another idea or repeating the same explanation.
Wezy lets agents enroll a compatible request and signed-in customers add or withdraw their own vote. The team can then compare customer volume with distinct represented organizations and recent demand. That answers “who is asking for this request?” before the broader product decision.
Wezy supports company-managed JSM Cloud projects. It does not provide anonymous voting, a public request catalogue or broader access to private requests. If this is the missing step in your service workflow, evaluate Wezy on Marketplace.
A practical workflow using both
Use a deliberate handoff rather than two competing backlogs:
- Triage in JSM. Check the request’s meaning, urgency and audience. Incidents and contractual commitments keep their own service priorities.
- Collect request demand where appropriate. Enroll selected requests and keep sharing rules suitable for the intended customers.
- Review the evidence. Look at votes, organization breadth and the actual customer problem. Record exceptions instead of treating a score as the decision.
- Associate the product opportunity. Use a JPD idea and add relevant service evidence through a supported, tested process.
- Make the product decision. Consider strategic fit, effort, risk and other discovery evidence alongside demand.
- Communicate through the service workflow. Give customers a clear outcome without turning every vote into a delivery promise.
This is a proposed operating process. We have not verified automatic synchronization of Wezy votes, scores or organization weights into JPD. Keep any manual handoff explicit, and validate custom automation separately.
Check external sharing before promising participation
JPD’s published-view documentation supports sharing with external audiences under defined plan and access settings. It also lists limitations, including Votes among unsupported fields for published views.
Distinguish seeing a roadmap from participating in a product space and voting on a JSM request. Test the exact stakeholder account and intended action. A public link should not be treated as proof that every interaction available to a product team is available to an external viewer.
Choose the smallest workflow that answers the question
If product discovery already receives the evidence your team needs, improve that process before adding another app. If your missing signal is customer support on accessible JSM requests, evaluate request-level voting. If both decisions exist, connect them with a named owner and a clear handoff.
Our JSM voting app checklist helps you define acceptance criteria before installing.
Frequently asked questions
Can JPD collect feedback submitted through JSM?
Yes. Atlassian documents creating ideas with Automation and adding JSM requests as insights. Choose the route that fits your triage process and test its configuration.
Does Wezy replace Jira Product Discovery?
No. Wezy focuses on customer demand on enrolled JSM requests. It does not replace JPD’s wider idea assessment, roadmap and product-discovery workflow.
Do votes automatically become a roadmap commitment?
No. They are evidence of expressed demand. Your team still decides what to build, considering impact, effort, obligations and strategic fit, then communicates the decision.
Published by the team behind Wezy Customer Voting. Product capabilities are linked to their official documentation; worked examples are illustrative.
Let customers vote on your JSM portal.
Install Wezy from Atlassian Marketplace, open one request for voting and see the first vote in Jira.