Skip to the guide

JSM role-based troubleshooting

JSM Organization Missing After a Vote: A Diagnostic Guide

Diagnose a missing organization in Wezy voting by checking saved support, customer membership, service desk association and project allowance without widening access.

Wesy November 11, 2026 5 min read

In short

A saved vote and its optional organization attribution are separate states. Confirm the vote first, then identify which organization eligibility or reading check is missing. Never share a private request simply to populate a selector.

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

When an organization is missing after a Wezy vote, first check whether the vote itself is confirmed. Organization attribution is optional and comes afterward. A customer can have a saved vote even while the organization list is unavailable; withdrawing and re-voting is not the default repair.

This guide isolates an attribution problem in a company-managed JSM Cloud project. If the customer cannot open the request at all, start with the request-permissions guide, not the selector.

Separate three questions that look like one problem

A support report often says “my company is missing,” but that can describe three different states:

Question Evidence to read What it establishes
Did the customer save support? The confirmed voting state, such as You voted Whether the vote is recorded
Is an organization eligible for this customer and project? Membership, service desk association and Wezy allowance Whether it may be offered for attribution
Did the customer save the attribution? The saved organization shown after the operation Which organization the active vote represents

According to Wezy’s attribution documentation, an unattributed vote contributes to V but not to O or W. No organization is selected automatically, even if exactly one is eligible. A displayed option is not the same as a saved choice.

Follow the shortest diagnostic path

The vote is confirmed, but the organization list failed to load

Preserve the saved vote. Read the message and use Retry organizations when offered. The documented behavior keeps the confirmed vote saved when organization reading is unavailable.

An unavailable read is not evidence that the customer belongs to no organization. Record the exact message, role, screen and time. After a session expiry or concurrent change, reread the updated state rather than clicking through assumptions.

The list loads, but the expected organization is absent

Have the appropriate administrator check the three eligibility conditions independently:

  1. Membership: does this exact signed-in customer belong to the expected JSM customer organization?
  2. Service desk association: is that organization associated with this service project?
  3. Project allowance: is it allowed by the saved Wezy configuration for this project?

The conjunction matters. “The organization exists somewhere on the site” is not a pass for all three checks. Atlassian’s organization-association guide and customer-membership guide describe different administrative operations.

Where the interface reports missing JSM organization-reading authorization, let the authorized agent or administrator resolve the indicated permission. Do not ask a customer to share administrator credentials or broaden their role to make a test succeed.

One organization appears, but the dashboard still shows no organization

The customer still needs to choose Link vote to [name]. For multiple choices, use Add your organization, select one and Save organization. Choosing a row without saving is not a completed attribution. In the portal list, Back discards an unsaved organization choice while retaining the saved vote and previously saved attribution.

Read the confirmed attribution afterward and refresh the relevant Wezy view. A separate Jira field or search result may still be behind; do not alter app-managed fields to imitate the expected result.

Do not confuse association, attribution and sharing

Adding an organization to a service project, linking a vote to it and sharing a request with it are different actions. Atlassian warns that adding an organization to a request shares the request with that organization’s members. That is not a harmless way to refresh a missing selector. See the official organization guidance.

Wezy attribution does not grant Jira access. Weights do not grant access either. Any legitimate membership, association or allowance correction should follow the team’s existing access policy; none should be made just to produce a larger organization count.

Use a controlled example to verify the explanation

Suppose a test request has two confirmed votes. Alice belongs to ExampleCo and chooses it; Bob leaves his vote unattributed. The illustrative expected result is V = 2 and O = 1.

If Bob also legitimately represents ExampleCo and saves that attribution, V remains 2 and O remains 1. There are still two people and one distinct represented organization. If Bob instead saves an eligible different organization, V remains 2 and O becomes 2.

These are proposed checks with fictional accounts, not executed customer results. They show why “the organization count did not increase” can be correct behavior rather than a failed save. The organization-demand guide explains the separate Advanced weight calculation.

Keep a small evidence record

For one affected account and one request, record:

Observed vote state:
Organization list: available / unavailable / expected option missing
Membership checked by:
Service project association checked by:
Saved Wezy allowance checked by:
Attribution action and confirmation:
Observed V/O before and after, with time and timezone:
Exact error or unresolved check:

Keep identifiers and screenshots in an access-controlled location. A support summary normally needs the role, edition, app version, affected screen and exact message—not a full customer export, API token or private request description.

When the three eligibility checks pass but the offered retry and reread do not resolve the discrepancy, use Wezy support with that bounded evidence. Avoid uninstalling the app or repeatedly changing memberships as a diagnostic experiment.

Assign each check to someone who can verify it

Check Appropriate owner Evidence to keep
Saved vote and saved attribution The signed-in customer, with support guidance Displayed confirmation and observation time
Organization membership and service association An administrator authorized for those JSM controls Exact account/organization association checked, not credentials
Wezy project allowance and available edition/state Authorized project administrator Saved configuration and any displayed restriction
Unresolved read or save discrepancy Support with a bounded reproduction Exact message, role, version and failed step

A customer cannot be expected to repair an administrator-only gate. Keep the checks separate so “the customer tried again” does not get recorded as proof that membership, association and saved project allowance were all verified.

What success looks like

The customer can distinguish saved support from optional attribution; the eligible organization is offered under the intended permissions; the saved choice produces understandable V and O values. A successful fix does not require making the request more public or forcing every voter to represent a company.

Wezy Customer Voting’s Marketplace listing describes this separation: portal voting on accessible enrolled requests, with optional representation of an eligible organization. Preserve that boundary when troubleshooting.

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