Skip to the guide

JSM prioritization framework

Prioritize JSM Feature Requests Beyond Ticket Counts

Build a practical Jira Service Management feature-request review using customer votes, organizations, recency and an explicit decision record with Wezy.

Wezy Team Updated October 23, 2026 5 min read

In short

Separate operational urgency from product demand. Compare votes, distinct organizations and recent support, then document the impact, effort and decision rather than treating the highest score as a delivery commitment.

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

A busy Jira Service Management queue answers an operational question: what needs attention? A feature-request review asks a different question: which improvement would solve a meaningful problem for customers? Counting tickets alone mixes repeated contacts, separate organizations, incidents and product suggestions into one number.

Use a two-stage review. First handle requests that require operational action. Then compare eligible improvements using customer demand and a written assessment of value, feasibility and constraints. The method below is a suggested team process, not an automatic Jira workflow or a claim about customer results.

Keep incident priority separate from feature demand

Atlassian describes JSM priority in terms of operational importance, including impact and urgency. Customer popularity is a different signal. A service outage with no votes can require immediate action; a popular reporting enhancement can still wait for a planned release.

Before scoring, put each request into an appropriate review lane:

Lane Review question What to do with votes
Incident or active service disruption What is affected and how urgent is restoration? Do not wait for votes to act
Security, legal or contractual obligation What obligation applies, and who owns the decision? Keep demand as context, not the deciding condition
Defect needing investigation What is broken and what evidence is missing? Use votes alongside reproducibility and affected scope
Product improvement What problem would this solve, for whom, and at what effort? Compare demand across similar requests

This separation prevents an attractive feature ranking from silently replacing your existing service commitments.

Create one reviewable problem statement

Describe the outcome before suggesting a solution. “Export filtered requests without rebuilding the report” is more useful than “Add a new button.” Record the current workaround, who is affected and an example of the workflow. Ask for enough context to compare needs without collecting unnecessary customer data.

For duplicate submissions, nominate a reference request only after checking visibility. Linking two Jira work items is not permission to expose either request to another organization. The duplicate-request workflow explains how to keep a shared problem separate from confidential customer details.

Then decide which requests are suitable for voting. In Wezy’s documented workflow, an administrator configures eligible request types and open statuses, and an agent explicitly enrolls each request after reviewing its content and sharing. Saving project rules does not enroll every ticket.

Compare three demand signals before interpreting a score

Wezy Standard uses a fixed formula:

Demand score = V + 3 × O + 2 × R30

V is the number of active customer votes. O is the number of distinct organizations represented by eligible active votes. R30 counts eligible active votes first activated within the last 30 days. The official scoring guide explains these definitions and the configurable Advanced formula.

R30 overlaps with V: a recent active vote contributes to both terms intentionally. It is not an additional unique voter. An unattributed vote contributes to V, without adding an organization to O.

Consider this illustrative example, calculated with the Standard formula:

Request V O R30 Calculation Score
A: add a dashboard export 12 1 8 12 + 3 + 16 31
B: improve organization reporting 8 5 6 8 + 15 + 12 35
C: add another notification option 20 2 1 20 + 6 + 2 28

Request C has the most votes. Request B leads this particular demand ranking because support spans more organizations and includes more recent active votes. Neither finding tells you implementation cost or commercial value. Read the component metrics before explaining why a request ranks first.

Add the decision context the formula cannot know

Use a short review record rather than pretending that every input can be measured precisely:

Field Useful evidence Avoid
Customer problem Specific blocked workflow and workaround Repeating the proposed feature name
Demand Votes, represented organizations, recent support, date checked Treating unavailable data as zero
Impact What changes if the problem is solved Invented revenue estimates
Effort and dependency Engineering assessment, uncertainty, prerequisite work A precise delivery date before assessment
Decision Investigate, plan, defer or decline, with an owner Letting the score imply a commitment

Wezy supplies a demand signal; your team supplies the assessment and decision. If effort is unknown, record “needs investigation” rather than manufacturing a value so the request fits a ranking spreadsheet.

Run a repeatable review meeting

  1. Review exceptions first. Check incidents and obligations outside the feature-demand ranking.
  2. Refresh the candidate set. Confirm project, filters, eligibility and request visibility before comparing results.
  3. Explain changes. Examine whether a shift came from new support, withdrawals, organization attribution, aging beyond 30 days or a formula change.
  4. Investigate a manageable shortlist. Choose the requests your team can assess properly, rather than committing to everything above an arbitrary threshold.
  5. Record the reason and next review. Leave a trace that another agent can understand later.

Use consistent filters when comparing periods. Historical analysis also depends on recorded coverage; installing an app does not create a year of past observations. The organization-weighting example shows why a changed coefficient must not be mistaken for changing customer demand.

Close the loop without promising delivery

A useful customer update might read:

We have recorded your support for this request. The team is reviewing the problem alongside customer demand, effort and existing commitments. Voting helps inform that review; it does not confirm a delivery date. We will update this request when a decision is available.

This is a suggested communication template, not an automatically sent Wezy notification. Adapt it to the channel and request audience. Keep internal commercial discussion in an appropriate internal location.

If you need customer votes within your existing company-managed JSM Cloud portal, review Wezy on Atlassian Marketplace, then validate the workflow with the pilot checklist.

Frequently asked questions

Should the highest demand score always become the highest Jira priority?

No. Demand and operational priority answer different questions. Use customer support as evidence in a product review; preserve your impact, urgency and service-management rules for operational work.

Can a request’s score fall without losing a vote?

Yes. An active vote can age out of the R30 window. With the Standard formula, its recent-vote contribution disappears while its active-vote contribution remains. Examine the metrics and observation date before describing a decline as lost support.

Can Wezy replace a product discovery process?

Wezy measures customer demand on eligible JSM requests. It does not supply effort estimates, research validation or a delivery roadmap. Teams needing those workflows can evaluate a complementary discovery process; see Jira Product Discovery versus JSM feedback.

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