Skip to the guide

JSM worked example

Organization-Weighted Voting in JSM: A Worked Example

Learn how votes, organizations and weights differ in Jira Service Management, with a reproducible Wezy score example and checks before activating Advanced.

Wezy Team Updated October 23, 2026 5 min read

In short

Organization-weighted voting separates individual support from the breadth and chosen importance of represented organizations. In Wezy Advanced, each represented organization contributes its weight once; several employees do not multiply that organization's weight.

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

Nine votes from one organization and nine votes from nine organizations describe different patterns of demand. Neither is automatically more valuable. A B2B service team needs to see both individual support and organizational reach, then decide whether an explicit weighting policy is useful.

This worked example explains how Wezy separates those signals. The figures are hypothetical and reproducible; they are not customer benchmarks, adoption statistics or a recommendation to assign a particular client a particular weight.

Distinguish votes, organizations and weighted demand

The Wezy scoring documentation defines four inputs:

Input What it measures What it does not measure
V Currently active customer votes Number of companies or tickets submitted
O Distinct organizations represented by eligible active votes Every organization associated with the project
W Sum of represented organization weights, once per organization Votes multiplied by the selected organization’s weight
R30 Eligible active votes first activated within 30 days Every click or vote change during the month

A customer’s organization attribution is optional. An unattributed vote still contributes to V. It does not silently infer an organization from an email domain, populate O or assign a weight on the customer’s behalf.

Organization attribution also does not change access. Atlassian’s description of portal sharing concerns request visibility; selecting an organization in Wezy concerns the demand expressed by an authorized voter. Keep those two decisions separate.

Start with the fixed Standard score

Standard uses:

S = V + 3 × O + 2 × R30

Assume an eligible request has nine active votes. Some of those votes represent Organization A and some represent Organization B. The remainder are unattributed. Three active votes were first activated in the last 30 days.

The inputs are V = 9, O = 2 and R30 = 3. Therefore:

S = 9 + 3 × 2 + 2 × 3
  = 9 + 6 + 6
  = 21

The result is a demand score, not a percentage and not a promise about how quickly the work will be delivered. Standard does not add weighted organization demand to this formula.

Add organization weights with Advanced

Advanced allows an explicitly configured formula:

S = a × V + b × O + c × W + d × R30

For illustration, choose coefficients a = 1, b = 3, c = 2 and d = 2. Assign Organization A a weight of 4 and Organization B a weight of 1. Both organizations are represented by the request’s active votes, so W = 4 + 1 = 5.

Contribution Calculation Result
Active votes 1 × 9 9
Represented organizations 3 × 2 6
Weighted organization demand 2 × (4 + 1) 10
Recent active votes 2 × 3 6
Total 9 + 6 + 10 + 6 31

The score moves from 21 to 31 because the formula changed, not because ten customers appeared. This distinction matters when discussing a ranking with account teams or comparing screenshots from before and after activation.

Download the example CSV to inspect the inputs and contributions outside the article. It contains illustrative data only.

Test what happens when another employee votes

Suppose another eligible customer from Organization A adds a first-time active vote within the current 30-day window. V becomes 10 and R30 becomes 4. O remains 2 and W remains 5: Organization A was already represented.

With the same illustrative Advanced coefficients, the new score is:

S = 1 × 10 + 3 × 2 + 2 × 5 + 2 × 4 = 34

The extra vote adds three points: one from V and two from R30. It does not add Organization A’s weight again. A further vote first activated outside the 30-day window would have different consequences; do not assume reactivation resets that first-activation date.

Agree on a weighting policy before configuring it

Weights encode a choice by your team. They are not an objective measure of customer importance generated by the app. Before activation, write down:

  1. The decision the ranking supports. For example, comparing improvement demand during a quarterly review, rather than setting incident severity.
  2. The basis for a segment. Use a clear, consistently applied business category instead of ad hoc exceptions for the loudest stakeholder.
  3. Who can change weights. Record the owner and review expectations outside the app where appropriate.
  4. How to explain exceptions. A high-weight organization should not make a security obligation or critical incident depend on a vote count.
  5. How comparisons will be interpreted. Record the formula and effective configuration when exporting or discussing a ranking.

Do not add sensitive commercial details to a customer-visible request merely to justify a weight. The permissions checklist helps distinguish internal assessment from portal content.

Configure, preview and activate deliberately

In the Advanced configuration guide, project administrators set coefficients, create organization segments and assign weights. A specific organization override takes precedence over its segment weight. An organization without a segment or override uses the default weight of 1.

Coefficients and weights accept values from 0 to 10, with up to two decimal places. A weight of zero removes that organization’s weighted contribution; it does not erase its vote or remove the organization from O. Check whether the active formula still gives those other signals a contribution.

Use the available ranking preview to inspect representative requests. An Advanced edition and saved configuration can coexist with Standard scoring until Advanced is explicitly activated. Confirm the active scoring state, rather than assuming the edition name tells you which formula is running.

For a controlled evaluation, view Wezy on Atlassian Marketplace and follow the pilot checklist on a compatible company-managed JSM Cloud project.

Frequently asked questions

Does one organization get only one vote?

No. Individual eligible customers can each hold one active vote per request. Several customers may attribute their votes to the same organization. That increases V, while the organization is counted once in O and its weight once in W.

Will organization weights expose requests to other customers?

No. Attribution and weights do not grant JSM request access. Organization membership, service-desk association and the project’s attribution allowance must be verified for the selector, while existing JSM access governs which requests a customer can view.

Can I compare Standard and Advanced scores as a growth metric?

Not directly. Their formulas can differ, so a higher number may reflect configuration rather than additional demand. Compare the underlying metrics, observation dates and active formula before interpreting a change.

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