JSM comparison and measurement guide
Jira Service Management Voting vs CSAT Surveys: Which Feedback?
Compare customer voting, CSAT and surveys in Jira Service Management. Learn when to collect feature demand versus service satisfaction without mixing metrics.
In short
Customer voting answers which requested improvements matter; CSAT measures a service interaction; broader surveys explore experience. Keep each signal and audience separate.
In this guide
Use customer voting to measure demand for a proposed change, customer satisfaction (CSAT) to measure a service experience, and a survey to ask broader questions. These are not interchangeable scores. A customer might give a support agent five stars for helping them while still voting for a missing feature that causes recurring work.
This guide helps teams design a feedback measurement system inside Jira Service Management (JSM) Cloud. It is distinct from our guides on prioritizing feature requests and building a monthly demand report.
Three questions, three different feedback mechanisms
| Mechanism | Question it answers | Typical timing | Misinterpretation to avoid |
|---|---|---|---|
| JSM customer satisfaction (CSAT) | Was this particular service interaction satisfactory? | After a request is completed | A five-star rating means the product roadmap is fine |
| JSM surveys | What was someone’s experience with a process or service? | At an appropriate journey milestone | A survey response is automatically a product commitment |
| Customer voting for requests | Which existing proposed changes have customer support? | During feature-demand review | The most votes must be developed next |
Atlassian’s CSAT documentation describes a customer rating and optional comments associated with a completed request. Its Surveys documentation describes a configurable way to collect experience feedback. Those are Atlassian features, not functionality developed by Wezy.
Wezy Customer Voting is a separate app for recording support for eligible existing JSM requests and comparing demand. A vote is neither a CSAT response nor a promise to deliver a feature.
When to use JSM’s built-in CSAT
A support manager wants to know whether requesters were helped efficiently and respectfully. CSAT fits this question better than votes.
In JSM Cloud, an enabled CSAT survey is included with the relevant resolved-request notification. Atlassian describes administration under Space settings → Request management → Customer satisfaction and the default satisfaction report. Exact labels and triggering behavior can depend on your project type, workflow and notification configuration; test your instance. Atlassian CSAT setup.
Consider an illustrative incident: a customer asked why their invoice failed, and the agent fixed it quickly. The customer rates the interaction 5/5. That is evidence about the help experience—not evidence that an invoice-export enhancement is unnecessary.
Use CSAT trends to investigate service quality, request types and follow-up gaps. Atlassian provides satisfaction reports and customization guidance. Avoid treating a handful of ratings as a representative survey of every customer.
When to use broader JSM surveys
A project owner wants to know why onboarding is confusing. A survey can ask about handoffs, documentation or missing instructions, even when no single feature request already exists.
Atlassian’s built-in Surveys feature has a no-code builder, templates and mechanisms to share survey links. It must be activated when absent and its access settings must be reviewed. Atlassian’s survey getting-started guide. Availability and controls should be verified against the merchant’s current Atlassian edition and UI rather than inferred from this article.
Keep questions focused. For example:
- “Which onboarding step required the most assistance?”
- “What information was missing when you attempted that step?”
- “What single change would have prevented a support request?”
These are original sample questions, not an Atlassian-provided questionnaire. Free-text feedback may identify a feature gap that deserves a separate reviewable request.
When customer voting adds something different
Voting is useful after a concrete request exists and a team needs to compare demand across requests. Wezy’s documented scope is Jira Service Management Cloud, company-managed projects, using the existing portal and requests. An administrator configures eligibility, agents enroll an accessible request, and signed-in customers who already have access can vote. The app does not open requests to everyone or build an anonymous public feature board. See the Wezy setup guide.
An illustrative project has three requests:
| Request | Votes | Distinct organizations | Service CSAT |
|---|---|---|---|
| Add invoice CSV export | 18 | 7 | Not a vote attribute |
| Improve onboarding instructions | 11 | 9 | Not a vote attribute |
| Offer another report filter | 23 | 2 | Not a vote attribute |
The table uses invented example data to illustrate interpretation. The third request has the most votes, but fewer organizations represented. This is a prompt for product review, not an automatic verdict about reach or commercial value. Review impact, effort, security and customer context independently. Voting permissions guide.
Turn raw feedback into a vote-worthy request
Do not publish an unedited customer survey comment as a product request. Use a small conversion checkpoint:
| Raw feedback (illustrative) | Clarifying question | Possible next record |
|---|---|---|
| “The portal is confusing” | Which task and exact step failed? | Service improvement or documentation fix |
| “I need CSV export every month” | Which records, columns and permission scope? | Scoped feature request for review |
| “The agent solved it immediately” | Was anything still missing? | Positive CSAT evidence, not necessarily a feature vote |
Once a request is clear and approved for the intended audience, an authorized agent can enroll it for voting under the documented project rules. Neither collecting a survey response nor opening a Jira request automatically enrolls it in Wezy voting. Keep confidential details out of the customer-visible request and verify JSM sharing before inviting participation.
A practical feedback-to-roadmap workflow
- Resolve support requests through normal JSM processes and collect CSAT when appropriate.
- Review recurring themes in low ratings or survey comments without treating them as feature votes.
- Write one clear improvement request describing the problem and affected users, excluding confidential customer data.
- Confirm request sharing and voting eligibility before enrolling it in Wezy.
- Invite only an authorized audience to review and vote on the accessible request through a channel your team controls.
- Review demand and feasibility in a recurring product meeting; retain a decision owner.
- Reply with the actual outcome to the appropriate request audience. Do not assume that every voter is subscribed to notifications.
Atlassian separates customer notification recipients by roles, sharing and participation. A vote in Wezy is not proof that a recipient will get native Jira email. Review the notification behavior documentation before sending outcome updates.
Keep reporting denominators and identities separate
Do not merge a CSAT rating average with a feature-vote count into one “customer happiness” number. They measure different things and may have different audiences. Instead, show separate indicators:
| Signal | Example measure | Interpret with |
|---|---|---|
| Service quality | CSAT average for completed requests | Responses, sample size and request type |
| Process friction | Share of a survey’s respondents mentioning onboarding | Survey audience and question wording |
| Product demand | Votes and organizations supporting an eligible request | Eligible audience, request access and coverage |
| Decision follow-through | Approved requests with a customer-visible update | Review period and communication policy |
A trend only means something if the collection method and audience are comparable over time. Do not treat missing historical Wezy data as zero demand; review the monthly reporting guide for coverage constraints.
Before rollout: test audience and customer experience
With controlled, non-sensitive accounts, check that the intended customer receives the CSAT invitation, the intended survey audience can respond, and only an authorized portal customer can see and vote on the relevant request. Confirm separately which reply notifications get sent. Do not use an administrator account as a substitute for a customer’s view.
These are proposed test steps, not a report of a completed installation.
FAQ
Does JSM already include customer voting for feature requests?
JSM includes satisfaction and survey mechanisms, but those are not equivalent to Wezy’s request-level customer demand voting. Compare your actual needs, permissions and available tools before adding an app.
Can good CSAT coexist with strong feature demand?
Yes. CSAT is about an interaction; voting is about a proposed change. Both can be high without contradicting each other.
Does voting send all voters release notifications automatically?
Do not assume so. Review JSM’s request sharing, participants and notification settings, and confirm any separate communication integration.
Next step: write down the question you want to answer first. Use native JSM CSAT or surveys for experience feedback, then evaluate Wezy Customer Voting for JSM if you need structured demand for accessible requests.
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.