Skip to the guide

JSM setup guide

How to Add Customer Voting to Your JSM Portal

Let customers support existing requests with one click from your Jira Service Management portal. Your team then compares votes and organizations in Jira, with your current JSM permissions unchanged.

Wezy Team Updated October 30, 2026 4 min read

In short

Install Wezy Customer Voting from Atlassian Marketplace, choose which request types and statuses can receive votes, then open a request for voting. Customers who can already see that request vote in one click from the portal, and your team reads the result in Jira.

Runs on Atlassian
Company-managed JSM Cloud Existing JSM permissions apply
In this guide
What your customers seeCustomer portal
Example: customers want CSV exports.

A customer wants to export service requests to CSV. They find that existing request in the portal and choose Vote to show that the improvement matters to them. Your team sees the demand in Jira.

Wezy customer portal request Export service requests to CSV with aligned Open and Votes: 1 indicators, You voted confirmation, Withdraw my vote, Back and an optional organization button.
Current portal interface with sample data: a recorded vote and optional organization. Desktop: native capture from our test portal using the published app build. Mobile: an interface illustration for readability. View full size ↗
  1. Choose a requestThe title explains the improvement.
  2. Vote onceThe vote supports that existing request.
  3. See your choiceAfter the vote is saved, Wezy shows You voted. Linking an organization is optional.

Before you start

  • A company-managed JSM Cloud project. Team-managed projects, Data Center, Atlassian Government Cloud and Isolated Cloud are not supported.
  • The right administrators. Someone who can install Atlassian apps on your site, and a project administrator.
  • A test customer account that can already open one request in the portal. An agent's view in Jira does not show the customer journey.

Why an app? Jira's built-in Vote action is used from the Jira work item view. Atlassian's suggestion to let customers vote on the portal, JSDCLOUD-1743, was still under review on 23 October 2026.

Compare Jira votes and portal voting

Set up customer voting in 5 steps

  1. Site admin

    Install Wezy from Atlassian Marketplace

    Open the Wezy Customer Voting listing, choose Try it free and follow Atlassian’s installation flow for your site. Atlassian shows the permissions, editions and trial terms before you confirm.

    Try it free on Atlassian Marketplace Installing requires the appropriate Atlassian administrator permissions on your site.

    Then open your JSM project, go to Project settings → Wezy Customer Voting and check that the settings load.

  2. Project admin

    Choose which requests can receive votes

    In Voting rules, turn on Enable voting in this project, then choose:

    • the allowed request types, for example Feature request;
    • the workflow stages: New, In progress or both;
    • the Jira statuses allowed in those stages.

    Finish with Save settings. A changed switch is only a draft until you save. Completed requests cannot receive new votes.

    TipStart narrow: one request type and one status make your first test easy to check.

    Project settingsWezy Customer Voting
    Illustration of the voting rules: enable voting, allowed request types, workflow stages, allowed Jira statuses and Save settings, fictitious data.
  3. Agent

    Open a request for voting

    Open an existing request in Jira, then the enrollment panel for Wezy Voting. Review what customers can read and who the request is shared with, tick I have reviewed this request’s content and JSM sharing settings, then choose Open this request for voting.

    Saving the rules does not open every request: your agents choose. Opening voting never shares a request with new people.

    Jira requestWezy Voting enrollment
    Illustration of the enrollment panel with the review checkbox and Open this request for voting, fictitious data.
  4. Customer

    Customers vote in one click

    Customers who can already access the request vote from the Wezy list in the portal or from the request details: Vote, then You voted. No organization choice is needed first. See the customer view

    After voting, they can link the vote to their organization. It never adds a second vote. Back closes this panel without withdrawing the saved vote; Edit my vote opens it again. Each account has one active vote per request and can use Withdraw my vote at any time.

  5. Your team

    Read the results in Jira

    Use View the project results, or open the request’s Wezy Customer Demand panel. You see active votes, organizations represented and a demand score, so you can compare requests side by side.

    Votes are a demand signal, not a verdict. Weigh them with impact, effort and constraints. How to prioritize JSM feature requests

    Example requestCustomer demand in Jira
    Current customer demand panel excerpt showing a score of 30, 7 votes, 5 organizations and 4 recent votes. Sample data.
    Export service requests to CSV. Sample data: 7 votes, 5 organizations and 4 recent votes give a Standard score of 30.

Try it on your own portal

Install Wezy, open one request for voting and see the first vote in Jira.

Try it free on Atlassian Marketplace Free trial · Runs on Atlassian

If something doesn’t show up

A request is missing from the portal list
Check, in order: the customer's access to the request, the saved rules (request type and status), and whether an agent opened it for voting. Then use Refresh requests and Show more requests. An open request can still be unavailable to a customer who cannot access it.
No organization is offered after voting
The customer must belong to the organization, the organization must be associated with the service desk, and it must be allowed in Wezy's project settings. Attribution is optional: the vote counts without it, and no organization is selected automatically.
An error appears after clicking Vote
An error alone does not tell you whether the vote was saved. Read the current state. If Confirm my choice again appears, use it: it confirms the same vote without creating a duplicate.
Jira fields or JQL don't show the vote yet
Jira fields and search indexing can update after the vote is confirmed. Don't edit Wezy's app-managed fields by hand. The full documentation covers every state.

Frequently asked questions

Does installing Wezy make my requests visible to customers?
No. Existing JSM access still applies, and agents open requests for voting one by one. See the permissions checklist.
Do customers need to choose an organization?
No. Customers vote first. Linking an organization is optional and never adds a vote.
Does the most-voted request win?
No. Votes show customer demand. Your team still decides with impact, effort and constraints.
Which JSM setups are supported?
Company-managed projects in Jira Service Management Cloud. Team-managed projects, Data Center, Atlassian Government Cloud and Isolated Cloud are not supported.
Where can I see prices and trial terms?
On the Atlassian Marketplace listing, with the current editions and free trial terms.

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