JSM reporting workflow
Jira Service Management: Monthly Customer Voting Report
Turn JSM customer votes into a defensible monthly demand report. Export filtered Wezy results, distinguish votes from organizations and handle missing history.
In short
Prepare a monthly feature-demand report from Jira Service Management without mistaking demand scores for percentages or missing historical coverage for zero votes.
In this guide
A useful monthly Jira Service Management customer-voting report separates current support, organizational reach and recent activity before recommending priorities. Export only the requests your team is authorized to see, record the filters and scoring configuration, and label any missing historical coverage. Votes are evidence of customer demand, not proof of delivery priority, and a demand score is not a percentage.
This is a reporting procedure, not another voting-installation guide, pilot checklist or general prioritization framework. It uses the published behavior of Wezy Customer Voting for Jira Service Management, which supports company-managed JSM Cloud projects.
What to put on one page for decision-makers
A concise report can answer five questions:
- What was considered? Project, request types/statuses, review date and filters.
- What do customers support now? Current votes and distinct organizations represented.
- Is there recent activity? A supported recent-vote indicator, with coverage limits.
- What changed since the last review? Only compare like-for-like periods with sufficient history.
- What will the team do? Decision, owner, constraints and next customer update.
For a monthly review, define the snapshot cut-off and write it in UTC; avoid comparing a midnight UTC export from one month with an end-of-business local-time export from another. A top-five ranking without scope and dates is easy to misread. For example, a request that was removed from voting may disappear from an “open requests” view without losing all historical support; that is a filter change, not automatically a customer-demand collapse.
Learn the metrics before sorting
Wezy’s product guide distinguishes the following measures. Names below are conceptual meanings; inspect the actual labels and CSV schema in your current edition.
| Signal | Meaning | Common reporting mistake |
|---|---|---|
| Customer votes (V) | Current individual support on the request | Calling a vote a unique paying organization |
| Organizations requesting (O) | Distinct organizations represented by active votes | Counting every employee from one company as a new company |
| Votes in last 30 days (R30) | Recent activity under the app’s documented rules | Assuming the same 30-day voters are new monthly unique customers |
| Demand score (S) | The active formula’s calculated ranking signal | Reporting it as a 0–100 percentage or as forecast revenue |
| Weighted organization demand (W) | Advanced signal applying configured organization weights | Treating W as available or meaningful in Standard |
In Standard, the documented formula is S = V + 3 × O + 2 × R30. Advanced can use a different formula, but it requires explicit activation by an authorized administrator. Retain the formula/edition in the report because otherwise a score change may reflect a configuration change rather than a change in requests.
Worked example: the score can drop with no withdrawn votes
Assume a hypothetical request currently has V = 8 votes, O = 3 organizations, and R30 = 2. Its Standard score is 8 + 3×3 + 2×2 = 21.
If those two recent votes simply age out of the rolling 30-day window, while the total eight active votes and three organizations remain unchanged, the score becomes 8 + 3×3 + 0 = 17. The score dropped by four; this example does not establish that two customers lost interest or removed their support.
These numbers are original illustrative arithmetic, not customer telemetry. The complete formula and definitions should be checked against the current Wezy documentation.
Prepare the CSV from a defined view
The documented Wezy workflow is:
- In the JSM project, open Wezy Customer Demand and choose the request types/statuses and minimum votes/score filters relevant to the review.
- Apply the filters and note them in the report header. Advanced offers additional organization/segment filters subject to the edition and access.
- Select Export requests; this export is scoped to the applied filters and the requests your role can access.
- Choose Prepare CSV, wait for the export to be ready, and then Save CSV.
- Record the edition, period, row count, export timestamp and file version next to the report.
These are the paths documented in Wezy’s current export guide, not steps tested in the reader’s site. If the prepared download link expires, the guide instructs users to prepare it again. Permissions and licensing are checked when the file is delivered.
Avoid promising a fixed column order or an exhaustive list of all Jira fields. Use the columns actually present in the downloaded file and document any manual enrichment from Jira separately.
Compare months only when history supports the claim
The guide documents 7- and 30-day trends in Standard, with 90-day windows and covered-period comparisons in Advanced. Daily analytical snapshots are retained for up to 90 days in Standard and 365 days in Advanced, subject to actual accumulation and retention.
Historical comparisons use complete UTC days with coverage. A newly installed app does not magically reconstruct six months of voting history. An uncovered day is not zero votes, and a missing comparison should not be displayed as a negative trend.
| Situation | Safe reporting treatment |
|---|---|
| Current totals available, no prior snapshots | Report today’s totals only; write “historical comparison unavailable” |
| Current and prior periods fully covered | Compare with identical filters, edition and definitions |
| One period partially covered | Mark the period incomplete; do not present a percentage change |
| Advanced formula was activated this month | Label the scoring change; avoid comparing raw scores as if unchanged |
| Organization segment weights changed | Record the policy date and report effect separately |
| Time windows use local dates in one export and UTC dates in another | Reconcile boundaries before calculating a trend |
For monthly discussions, it can be better to show current values plus an explanatory note than a misleading month-on-month percentage.
A sample executive table
The following is a fictional table. It illustrates report structure, not an output claimed to be produced automatically by Wezy.
| Request | Current votes | Organizations | R30 | Standard score | Decision owner / next step |
|---|---|---|---|---|---|
| JSM-101 — Bulk export | 8 | 3 | 2 | 21 | Product: investigate scope |
| JSM-114 — Mobile approval | 4 | 4 | 1 | 18 | Security + Product: evaluate |
| JSM-128 — Portal labels | 9 | 1 | 0 | 12 | Support: document workaround |
The scores are 8+9+4 = 21, 4+12+2 = 18 and 9+3+0 = 12. The first row is not necessarily the highest business priority. A security, feasibility or contractual constraint can outweigh the current demand signal.
A useful one-page commentary might say: “JSM-101 has the highest recorded Standard score within this month’s filtered scope. We are investigating complexity; there is no committed release date.” That is more defensible than “JSM-101 is approved because it won the vote.”
Keep the source, calculation and recommendation separate
A lightweight report package has three layers:
- Raw evidence: the authorized CSV, export date and filter note, kept in a restricted team location.
- Interpretation: the scoring version, coverage statement, changes in scope and known limitations.
- Decision: a named owner, rationale, status and customer-facing next step.
JSM access remains relevant. Atlassian documents customer/request access and organizational sharing as distinct controls. Do not widen customer permissions or publish a private issue description to make the report more convenient. Review Atlassian’s customer permissions guidance and our voting permissions guide.
If an organization is sensitive, share an appropriate aggregated report rather than forwarding raw per-request exports to an unnecessarily broad audience. Exports are copies: removing a file from the app cannot revoke a copy somebody already downloaded.
QA checklist before presenting the report
The following is a proposed internal review, not a claim that the checks ran on your Jira instance.
| Check | Evidence to preserve |
|---|---|
| Same project, request types and statuses as previous month | Saved filter parameters |
| Current totals reconciled with two sample requests | Request keys, sanitized values and review time |
| Standard or Advanced edition identified | Edition and active scoring formula |
| Historical periods are both fully covered | Available UTC coverage and dates |
| Export contains only authorized requests | Account role and access review |
| Rows counted once per request, not once per vote | Export row key / request identifier |
| Decision owner is named | Meeting decision log |
| Customer-facing message is reviewed | Link to authorized JSM public reply |
If the CSV contains multiple analytical rows for the same request, normalize by the real request identifier before counting. Do not assume the number of CSV rows equals the number of separate feature ideas without inspecting the export.
Where Standard ends and Advanced begins
Wezy Customer Voting lists dashboards, customer votes, organization demand, Jira fields and CSV exports in Standard. Advanced adds organization segments and weights, configurable scoring and broader historical analysis. Check subscription and data availability in Atlassian’s installation flow before planning a report that requires Advanced.
You can still make a useful current-state monthly report in Standard. Advanced-only historical comparisons should be labeled unavailable rather than replaced with a manual subtraction of rolling totals taken on mismatched dates. Just avoid calling it a fully reconstructed monthly history when the supported periods or snapshot coverage are insufficient.
Frequently asked questions
Can I treat the highest score as the team’s priority list?
Not without an explicit decision process. The score summarizes defined demand signals. It does not contain development effort, incident severity, security exposure or promised contract terms.
Why did my request’s score change when nobody withdrew a vote?
A rolling recent-vote contribution can age out, or the active formula/configuration can change. Verify the current metrics and scoring version before inferring a customer behavior change.
Can every voter see the report or request?
No. Voting does not automatically grant a customer access to another person’s JSM request. Keep customer permissions separate from internal reporting.
Next step: take one filtered Wezy CSV, record its date, scope and edition, and reproduce two request scores by hand. Then build a one-page review with decisions and owners. The step-by-step export documentation and Wezy marketplace listing are the starting points.
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.