Skip to the guide

JSM comparison

Jira Votes vs JSM Customer Portal Voting

Compare Jira work item votes with customer voting in a JSM portal. Understand audience, access, organization demand and what to test before choosing an app.

Wezy Team Updated October 23, 2026 5 min read

In short

Jira work item votes and portal customer voting serve different journeys. Compare the audience and demand signals before changing settings or buying an app.

Runs on Atlassian
Company-managed JSM Cloud Existing JSM permissions apply
In this guide

Jira work item votes and Jira Service Management customer portal voting are different journeys. Jira’s voting control expresses support from the Jira work item view. A portal voting workflow lets customers support requests through the portal, subject to their existing access. Choose by the audience you need to involve, then test that exact journey.

We publish this comparison as Wezy’s team. Our product is one option for signed-in customer voting in JSM Cloud, company-managed projects. This article explains that scope rather than ranking every voting product.

Does Jira already have voting?

Yes. Atlassian documents a Vote action in its JSM work item collaboration guide. Jira administrators can also control whether voting is enabled through Jira’s general app configuration.

Those facts do not establish that the same control is available to a portal-only customer. The screen matters: an agent opening a request inside Jira has not tested a customer’s portal experience.

At the time of this review, 23 October 2026, Atlassian’s Cloud suggestion JSDCLOUD-1743, “Ability to vote on an issue on Customer Portal” is Reviewing and unresolved. That is a dated status for a specific suggestion, not a guarantee about future releases, every Atlassian deployment or Marketplace extensions. Recheck the current product and your site before purchasing.

Compare the workflow you actually need

Decision Jira work item voting Wezy customer portal voting
Where support is recorded The Jira work item view The signed-in JSM customer portal
Main setup question Is Jira voting available to the intended users? Is the project compatible, configured and the request enrolled?
Request visibility Governed by the user’s Jira access Governed by the customer’s existing JSM request access
Organization demand Check separately against your requirements Optional attribution with membership, service desk and project allowance checks
What the signal means A user considers the work item important An active customer vote, optionally representing an eligible organization
What it does not decide Delivery commitment or implementation order Delivery commitment, impact, effort or implementation order

The right comparison is therefore not “does a vote icon exist?” It is “can the intended person support the intended request without moving into an unsuitable access model?”

Scenario 1: your team wants an internal preference signal

Suppose engineers and service agents already work inside Jira and want to express which improvement matters most to them. Start by checking the existing work item voting experience. A customer voting app may be unnecessary if internal preferences are the entire requirement.

Record which users can see the issue, where they cast the vote and what the team does with the total. Keep a separate note for customer evidence, such as a linked support request. Do not silently label internal votes as customer demand: the people and the reason for participating differ.

If the actual need is product discovery, idea comparison and discovery evidence, also evaluate the workflow described in Jira Product Discovery vs JSM feedback. A demand signal and a product decision process can complement each other.

Scenario 2: customers should support an existing JSM request

Consider a support portal where several customer organizations ask for the same export option. Agents want customers to support a reviewed feature request from the portal they already use.

With Wezy, the administrator selects allowed request types and open statuses. An agent checks the request content and sharing, then explicitly enrolls it. A signed-in customer with request access can save or withdraw a vote. Agents review active votes, represented organizations and demand scores. The full Wezy guide documents the individual controls.

This workflow is suitable when access should continue to follow JSM. It is not an anonymous public feedback board, a separate public request catalogue or a promise to expose every request to every customer. Review Wezy’s Marketplace listing against those requirements before installing.

Scenario 3: many votes come from one organization

Imagine three customers from Organization A support a request and one customer from Organization B supports another. The raw vote totals answer how many accounts support each request. They do not answer how widely demand is distributed among organizations.

Wezy distinguishes active votes from distinct represented organizations. If all three eligible customers attribute their votes to Organization A, that is three votes and one represented organization. Advanced scoring also offers configurable organization weights, with explicit activation after saving and previewing settings.

These are analytical signals, not revenue estimates. An organization weight should follow a documented team rule; it does not grant access or prove business value. See organization-weighted voting in JSM before designing a weighting policy.

Avoid three misleading comparisons

Comparing different accounts: an administrator’s successful click does not demonstrate that a portal customer can vote. Use separate account roles during evaluation.

Comparing different request visibility: one customer may see a request another cannot. A lower vote count can reflect the audience with access, not lower demand among everyone you serve.

Comparing counts without definitions: internal Jira votes, active customer votes, represented organizations and website CTA clicks are different events. Keep their names and reports distinct. None alone establishes that the requested feature has been delivered.

A practical decision test

Write one requirement sentence before choosing a tool: “A signed-in customer who can read our shared feature request should be able to support it without receiving agent access.” Then verify it with a real customer account, withdrawal and a second account lacking request access.

If that describes your need, use the customer voting app selection checklist to compare scope, visibility and operation. If your need is only a Jira work item preference, evaluate the existing Jira control first.

Frequently asked questions

Will turning on Jira’s global voting setting add Wezy to the portal?

No. Jira’s global setting and Wezy’s project configuration are separate. A Wezy setup also requires a compatible installation, saved rules and explicit request enrollment.

Can customer voting replace Jira issue priority?

No. Customer votes are evidence for a decision. Your team still owns issue priority, response obligations and delivery choices. Keep urgent incidents out of a popularity contest.

Can Wezy collect anonymous votes?

No. The documented workflow requires a signed-in customer with JSM request access. Choose a product designed for a public anonymous audience if that is your requirement.

To evaluate the portal workflow, open Wezy on Atlassian Marketplace and follow the first-vote setup guide.

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.

Runs on Atlassian Read the full documentation

The site works without optional cookies. Your choice is saved on this device for 180 days.

Read more about data and Google