JSM edition decision guide
Wezy Standard vs Advanced: Choose by the Decision You Need
Choose a Wezy JSM voting edition by your scoring, segmentation and history needs. Distinguish retained snapshots, available comparisons and formula activation.
In short
Standard supports current customer-demand reviews with a fixed formula. Advanced is relevant when a defined decision needs segmentation, controlled organization weighting or broader covered historical analysis—not merely a larger feature list.
In this guide
Choose Wezy Standard when your team needs to collect portal votes and review current demand with an understandable fixed formula. Choose Advanced when a specific decision requires organization segments, configurable weighting or the additional historical analysis. More configurable does not automatically mean more useful.
We publish Wezy, so this is a product decision guide, not an independent vendor ranking. Both editions concern company-managed Jira Service Management Cloud projects and retain existing request-access boundaries. Check current prices and subscription terms in the Atlassian Marketplace installation flow; no fixed price or trial duration is assumed here.
Start with the meeting you need to improve
Write the decision in one sentence before selecting an edition. These illustrative scenarios lead to different requirements:
| Team question | Capability required | Edition to evaluate |
|---|---|---|
| Which eligible requests have current customer support? | Votes, organizations, dashboard, fixed score | Standard |
| Can agents create a Jira queue from customer votes? | Published numeric fields and native JQL | Standard can supply the core fields |
| Do requests from a defined customer segment need a separate review? | Available organization/segment filters | Advanced |
| Should represented organizations carry explicitly different weights? | Segments/weights and a controlled scoring policy | Advanced |
| Can we compare a particular older period? | Supported window, actual coverage and retained snapshots | Evaluate all three, not the edition name alone |
These are capability choices, not claims about installed customers. Wezy’s edition table and Marketplace list the product boundaries. Native Jira queues and Automation are separate tools, not Advanced-only features supplied by Wezy.
Do not confuse three different history questions
Historical analysis has three independent conditions:
Was the data recorded? An installation begins accumulating available snapshots. A new subscription cannot create votes or observations from before that collection existed.
Was it retained? Standard retains analytical snapshots for 90 days; Advanced for 365 days. A retention horizon describes stored observations, not an assurance that every day has coverage.
Does the edition offer the requested analysis? Standard offers available 7- and 30-day trends. Advanced adds 90-day windows and covered-period comparisons. Standard’s 90-day retention does not by itself turn its interface into an Advanced 90-day comparison tool. These distinctions are documented under history and changing editions.
For example, a team starting its installation in November should not purchase Advanced on the assumption that it will reconstruct an October customer-demand baseline. Record the actual covered UTC dates before approving that reporting requirement.
Organization weighting creates an ownership responsibility
Standard’s formula is V + 3×O + 2×R30. It already distinguishes individual support, breadth across organizations and recent eligible active votes. Advanced adds the configurable formula aV + bO + cW + dR30, where W sums represented organization weights once each.
Before choosing Advanced for weighting, identify who owns the segment definitions, who approves overrides, and how changes will be explained. Weights are a team policy, not verified revenue or a customer entitlement. They also do not change Jira request access.
A team that cannot explain why one organization should count more heavily may be better served by Standard plus a written human review. A team with a defensible segmentation policy can use the calibration fixture to see whether its proposed coefficients produce the intended trade-offs.
An upgrade is not formula activation
Treat these as separate states:
| State | What it means | What it does not establish |
|---|---|---|
| Advanced edition is effective | The relevant commercial entitlement is available | The project is already using weighted scoring |
| Advanced settings are saved | A configuration exists for preview/activation | That this configuration controls the live score |
| Advanced formula is explicitly activated | The selected saved profile is active | That every resulting priority is the right product decision |
An authorized project administrator should inspect Current scoring, save and preview the intended settings, then activate deliberately. Reread the active state afterward. The activation procedure also provides Return to Standard score.
The preview may show only the first accessible requests. Use a known representative set rather than declaring a successful project-wide calibration from a small visible subset.
Plan a downgrade before changing the subscription
A confirmed downgrade restores Standard scoring, prevents new Advanced outputs and makes W non-applicable. The documented policy provides a 30-day recovery period before snapshots older than Standard’s 90-day retention are purged. Read the effective state and date in Data and privacy → Edition and retention rather than calculating a deadline from an informal email or an uncertain license message.
Before an authorized change, identify which historical records the team needs to retain, prepare the appropriate permitted exports and document the scoring-policy transition. A later upgrade does not recreate purged snapshots. An undetermined license state is not, by itself, the documented trigger for destructive handling. See the current retention policy in the product guide.
This is an operational checklist, not legal advice or a promise that every possible historical period is recoverable.
Choose an explicit next action
Stay with Standard when the fixed-score review meets the requirement and the team has no owned weighting or segmentation policy. Evaluate Advanced when the missing capability is documented there and someone will administer it. Wait for coverage when the capability exists but the required period has not been recorded. Repair configuration or access when the edition is effective but the intended saved settings, activation or authorization is missing.
These are four different outcomes. Buying a higher edition is not a repair for missing request access, and a longer retention period is not a substitute for an unrecorded baseline. Record which condition blocks the decision before changing the subscription.
Use an acceptance decision, not a feature score
For each must-have requirement, keep a short record:
Decision the team needs to make:
Required signal or historical period:
Edition capability documented:
Coverage actually available:
Owner of configuration and interpretation:
Pilot observation: passed / failed / not tested
Remaining limitation:
A useful Standard acceptance exercise is to reproduce a known request’s score and use it in a human review. An Advanced exercise adds a documented ranking comparison, an explicit activation check and a covered-period analysis when data exists. These are proposed exercises, not claims that your tenant has passed them.
Use the general voting-app evaluation guide for compatibility and access requirements, then the Marketplace listing for current commercial terms. The right edition is the one that supports an owned decision process without asking the data to say more than it knows.
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.