A customer asks for a dark theme. Others want it too. When that request reaches your product review, you need to know how many people support it and which customer organizations they represent.
I develop Wezy Customer Voting for Jira Service Management, which adds voting to requests in your JSM portal. Your team can see individual support and organization demand alongside the request.
Give customers a clear way to support a request
Once your team enables voting on a request, a customer signs in and selects Vote for this request. Each account has one active vote per request. Customers can withdraw their vote if their needs change.
With organization attribution enabled, customers can also choose an organization they are eligible to represent. Your team can then see which customer accounts are behind the demand.
Customers support a request and select their organization directly in the portal.
See how demand is spread across organizations
Five votes from one organization and five votes from five organizations describe different kinds of demand. Wezy keeps those counts separate.
Several colleagues can support the same request. Each active vote counts, while their organization is represented once. Votes without an organization still contribute to the total vote count.
In a B2B product review, that distinction helps you see whether interest is concentrated within one customer account or shared across several.
Review customer demand alongside the request in Jira.
Bring customer demand into the product review
Open the project’s Wezy Customer Demand page to compare requests by votes, represented organizations or demand score. Filters let you focus on a request type or status. You can open a request from the ranking to read the discussion behind the numbers.
Compare customer support across requests before deciding what to build.
The Standard score combines active votes, represented organizations and recent votes. Organizations carry extra weight, and recent votes help surface current interest. Your team still chooses the priority based on the request’s impact, delivery effort and existing commitments.
If your team needs to reflect differences between customer accounts, Advanced adds organization segments and weights. You can preview how a scoring change affects the ranking before an administrator activates it.
Start with a few requests
Wezy works with company-managed Jira Service Management Cloud projects. To set up your first requests:
- Enable voting in the project’s Wezy settings and choose the request types and statuses you want to include.
- Check each request’s content and JSM sharing settings, then enable customer voting from its enrollment panel.
- Open the request with an intended customer account, cast a vote and review the result in Wezy Customer Demand.
Customers vote on requests they can already access. JSM request participants and customer organizations continue to control sharing.
Choose a small set of feature requests your customers can discuss together, then bring their votes to your next product review.
Explore Wezy Customer Voting on Atlassian Marketplace
