Skip to the guide

JSM workflow change checklist

Changing a JSM Workflow Without Breaking Customer Voting

Review Wezy voting eligibility when JSM statuses or request types change. Map the old and new states, test customer access and keep a reversible change record.

Wesy November 11, 2026 5 min read

In short

A workflow change can leave a request readable but no longer eligible for new votes. Check saved request-type, stage and exact-status rules separately from enrollment and customer access, then test the transition paths you changed.

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

Treat a JSM workflow change as a change to voting eligibility, not merely a new status label. After adding or replacing a status, an enrolled request may still exist and remain readable while no longer matching the project’s saved Wezy voting rules. That is not necessarily lost data or a failed installation.

This checklist is for maintaining an existing company-managed JSM Cloud voting workflow. It is not another installation tutorial and does not claim that changing a workflow automatically changes Wezy settings.

Identify the layer you are changing

Keep the native Jira workflow separate from the customer-facing status wording and from the app’s eligibility rules. Atlassian documents how request-type workflow statuses can be customized. A familiar portal label is not sufficient evidence that the underlying status configuration is unchanged.

Wezy’s project configuration includes the enabled project, allowed request types, open workflow stages and exact allowed Jira statuses. An agent separately enrolls the request after reviewing its content and sharing. The customer must also already have Jira access.

A useful model is therefore:

Customer can access the request
+ project voting is available
+ saved type/stage/status rules permit the request
+ the request is explicitly enrolled
= a candidate for the supported voting journey

This is a diagnostic model, not an API contract. Read the actual displayed state for account, completion or maintenance restrictions rather than assuming the formula overrides them.

Build an old-to-new status map

Before applying a production change, record the affected request types, the actual Jira statuses and their categories, the saved Wezy rules and a small list of authorized test requests. Include a request with existing support so you can distinguish eligibility from the retained vote state.

Here is an illustrative mapping, not a recommended universal workflow:

Before After Intended voting policy Change to verify
Open Under review Accept new votes New status is explicitly allowed in the intended open stage
In progress Building Continue accepting support Saved rule matches the replacement status
In progress Delivered Stop new votes Completed state is not treated as open voting
Open Waiting for information Team decision required Do not assume every unfinished state should receive votes

Record identifiers where your administration tools expose them, not only display names. If several projects share a workflow, review each project’s Wezy configuration separately. The documentation does not promise a site-wide automatic synchronization of voting rules.

Make the smallest deliberate configuration change

Follow your normal Jira workflow change process. In Wezy, review the affected project rules, select the intended request types/stages/statuses and Save settings. An unsaved switch or selection is still a draft.

Do not enroll every request as part of the repair. Saving project rules does not enroll requests, and enrollment should still follow the agent’s content and sharing review. Reconfirm the known test requests individually.

Nor should you share a private request more broadly because it disappeared from a customer’s list. Access and eligibility are independent. The permissions checklist is the right place to investigate a true access discrepancy.

Test transitions, not just a static screenshot

Use an approved test environment or controlled test requests and separate customer and agent sessions. The following checks are proposed regression tests, not results observed on your site.

Test What to verify
Allowed request before transition Intended customer can read the request and the expected voting state
Transition to the new allowed open status Saved Wezy rules still permit the intended journey
Transition to a deliberately excluded status New voting is unavailable for the documented policy reason
Transition to completed work New votes are not accepted; do not interpret that as erasure
Existing voter revisits the request Saved support and offered actions are interpreted separately from new-vote eligibility
Unenrolled request in an allowed status It is not assumed to become enrolled automatically
Customer without request access The change does not expose private content
Agent dashboard and Jira queue Filters and queries still match the intended new statuses

For completed requests, Wezy can retain history without accepting new votes. Withdrawal is a separate customer action while access remains; removal from voting and erasure are different operations. Read the documented lifecycle, rather than deleting data to make a completed request disappear from a ranking.

If reopening is part of your workflow, explicitly test the returned request’s actual enrollment and allowed-state behavior. Do not infer that reopening alone restores every former voting or access condition.

Check downstream searches and rules

A JQL query containing the old status name may now select a different set—or none. A broad statusCategory != Done query may continue to return a request that the more selective Wezy voting policy excludes. Both can be behaving as configured.

Review the demand queue, saved filters and any vote-threshold Automation. Keep those review tools distinct from the app’s permission and enrollment decisions. Do not edit the app-managed vote fields or trigger repeated updates merely to accelerate indexing.

Keep an evidence record for the changed path

For each changed transition, record the starting and ending Jira status, the saved Wezy rule version or observation, enrollment state, test-account role, request key and the expected versus observed outcome. Use passed, failed or not tested rather than a single overall “works” checkbox.

A request that is readable but closed to new voting is a different result from a request that disappeared because the account lost access. If an unauthorized account can newly read private content, stop the rollout immediately and follow the site’s access-incident procedure; no correct vote count compensates for that failure. Preserve a sanitized record before making further configuration changes.

Decide whether to continue or roll back

Stop the rollout if a previously unauthorized customer gains access, an intended open transition cannot be explained, or the observed state conflicts with the saved policy. Use the supported Jira change procedure and your recorded prior Wezy settings to plan a controlled rollback; do not assume a workflow rollback reverses customer actions that occurred meanwhile.

Keep a concise change record: old/new status map, settings saved, test request keys, roles used, passed/failed/not-tested results, time, owner and rollback decision. This is more useful than “the voting page loaded.”

Wezy Customer Voting adds demand collection to existing JSM requests. Maintaining it successfully means carrying the eligibility policy through workflow changes—not allowing a new label to silently redefine who can vote on what.

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