JSM security checklist
JSM Customer Voting Permissions: Access Checklist
Check Jira Service Management customer voting permissions before rollout: request visibility, organization attribution, account roles, exports and access tests.
In short
Review request visibility separately from voting eligibility, then test an authorized customer and a customer without request access.
In this guide
Customer voting should preserve the intended audience for each request. With Wezy, enabling voting, enrolling a request and allowing organization attribution do not automatically share the request. A signed-in customer still needs JSM request access. Validate both a permitted journey and a denied journey before a wider rollout.
This operational checklist covers Wezy for JSM Cloud, company-managed projects. It is not a certification of your site’s security. Your administrators remain responsible for reviewing JSM configuration, sensitive content and app permissions. See the full Wezy guide for the documented product behavior.
1. Separate four different permission decisions
| Decision | Question to answer | A common mistake |
|---|---|---|
| Portal access | Can this customer enter the relevant portal? | Assuming sign-in grants access to all requests |
| Request visibility | Can this account read this particular request? | Assuming an organization label shares the request |
| Voting eligibility | Do saved rules, status and enrollment permit voting? | Assuming a visible request always accepts votes |
| Organization attribution | May this customer represent the selected organization? | Treating attribution as a sharing control |
Atlassian’s customer permissions documentation separates channel access from customer sharing. Review those settings without broadening them simply to make a vote button appear.
Record the intended audience in ordinary language: “Members of the customer organization involved in this request,” for example. Compare the actual JSM sharing against that statement. If the audience is unclear, stop enrollment until the request owner resolves it.
2. Check compatibility and role ownership
- The site uses JSM Cloud and the selected project is company-managed.
- An authorized administrator reviews installation permissions and subscription terms.
- A project administrator owns the saved voting rules.
- An authorized agent owns request review and enrollment.
- A customer account, separate from the agent journey, is available for testing.
Wezy’s supported scope excludes team-managed projects, Jira Data Center, Atlassian Government Cloud and Isolated Cloud. Customers must sign in; there is no anonymous voting or separate public request catalogue.
Review the current installation information on Wezy’s Atlassian Marketplace listing before approving the app for your site.
If you are still comparing products, check these boundaries against the customer voting app selection criteria. A product designed for open public boards addresses a different access requirement.
3. Review the request before enrolling it
Use a feature request whose description is appropriate for its audience. Remove private troubleshooting details from the customer-visible proposal before sharing through your established JSM process. Keep the relevant internal context in the appropriate internal location.
Then inspect participants, organization sharing and any applicable issue security. Atlassian’s JSM access guide notes that restrictive issue security can affect request access. Do not assume project membership settles every request’s visibility.
Check that the request matches Wezy’s saved type and open-status rules. In the enrollment panel for Wezy Voting, confirm the content and sharing review before selecting Open this request for voting. Enrollment does not grant a new audience access.
4. Run a permitted and a denied access test
Prepare two customer accounts that reflect your intended audience. Account A should have request access. Account B should lack access to that request. Use separate browser profiles so an existing administrator session does not invalidate the test.
| Test | Expected observation | Evidence to retain |
|---|---|---|
| Account A opens the portal request | It can read the intended content | Account role and sanitized screenshot |
| Account A opens Wezy and votes | The panel confirms saved support | Request key and observed state |
| Account B searches the voting list | The inaccessible request is not exposed there | Search/list observation |
| Account B opens the request’s direct URL | JSM does not expose the request content | Access result without private content |
| Account A withdraws | Its saved support changes | Confirmation and agent metric check |
If Account B can read the request, investigate JSM sharing and access first. Do not declare an app defect or assume voting created the access without comparing the before-and-after settings.
5. Test organization attribution independently
For an organization to be offered for attribution, Wezy checks customer membership, association with the service desk and the project’s allowed organizations. All three are needed. If JSM organization reading requires authorization by a permitted agent, complete that authorization through the offered flow and review it when permissions change.
Try a customer who belongs to an allowed organization and a customer who does not. The latter should not gain the ability to represent it merely because an agent allowed the organization in Wezy.
Attribution remains optional. A customer can vote without it when the panel permits voting. Neither organization selection nor an Advanced organization weight shares a request. See how organization-weighted demand works for the separate analytical meaning.
6. Check what happens when access changes
Use a controlled test request and record the original sharing before changing anything. Following confirmed access loss, a vote may be suspended and stop contributing to current metrics. Restoring access does not automatically reactivate the vote: the customer checks the state and uses Reactivate my vote when offered.
Test the actual displayed state rather than expecting a particular refresh deadline. A temporary read failure is not the same as confirmed access loss. Also distinguish a completed request, removed enrollment and an installation write suspension; these can affect voting for different reasons.
7. Treat exports and erasure as separate operations
An analytical CSV follows the exporting account’s accessible requests and active filters. Review its scope and store received files appropriately. A file already saved on a computer cannot be remotely revoked by Wezy.
Administrative data recovery and irreversible erasure have different permissions and purposes. Removing a request from voting does not delete the Jira request or erase Wezy data. Do not use erasure as a routine voting test. Follow the documentation’s target checks and warnings when authorized erasure is actually needed.
Frequently asked questions
Will allowing an organization reveal all its requests?
No. Wezy’s allowance controls eligibility for vote attribution. JSM request access and sharing remain separate. Test with customer accounts instead of inferring visibility from the settings label.
Can I validate access using only my administrator account?
No. An administrator’s view does not reproduce a customer’s access. Use an authorized customer and one without access, including the direct request URL test.
Is removing a vote the same as deleting personal data?
No. Withdrawal changes customer support. Erasure is a separate, authorized and irreversible administration operation within its permitted scope. Review the privacy policy before deciding what operation is required.
For a bounded evaluation, review Wezy on Atlassian Marketplace, then use the setup guide with this access checklist.
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.