JSM workflow and templates
Manage Duplicate Feature Requests in JSM: A Workflow
Organize duplicate Jira Service Management feature requests without exposing customer details. Use a reference request, demand review and communication templates.
In short
Keep the shared product problem separate from each customer's support conversation. Review visibility before using a reference request for voting, and do not assume links, duplicate resolutions or enrollment merge votes or grant access.
In this guide
A second request about the same improvement is useful evidence. A second request containing the same customer’s credentials, attachments and operational history is not necessarily a safe place to collect votes from everyone else.
The practical goal is to preserve each customer conversation while giving the team a coherent problem to evaluate. The workflow below uses a reference request where appropriate, explicit access checks and a decision log. It is a suggested operating process, not a Wezy feature that automatically finds, merges or closes duplicates.
Decide whether the requests describe the same problem
Two requests mentioning “reporting” may describe different needs. One customer wants to export records for an audit; another wants a live operational dashboard. Combining them prematurely can create a large vote count that does not support a clear implementation decision.
Use four triage questions:
| Question | Evidence to compare | Reason to keep requests separate |
|---|---|---|
| What outcome is blocked? | The task the customer cannot complete | Different underlying outcomes |
| Who needs it? | User role and workflow context | Different access or permission models |
| Is the workaround the same? | Current steps and their limitation | One is a defect, another an enhancement |
| What would count as solved? | Observable acceptance conditions | Different acceptance criteria |
Record “related, needs investigation” when you cannot yet establish equivalence. That is more useful than forcing every similar title into a single bucket.
Separate the shared problem from private evidence
A reference request should contain a clear, appropriate description of the common need. Private attachments, personal information and account-specific details can remain in the original support conversations with their original audiences.
Atlassian documents request-sharing options separately from internal work-item relationships. Review both the reference request’s current audience and the proposed audience before directing customers to it. Linking a duplicate or sending a portal URL does not itself establish that the recipient is allowed to view the target.
Use this reference-request template, adapted to information the intended audience may see:
Customer problem:
Who experiences it:
Current workaround:
Desired outcome:
What is outside this request's scope:
Team owner:
Current decision: collecting demand / investigating / deferred
Next review:
Keep the proposed decision labels in your team’s chosen fields or notes. They are suggestions, not additional statuses or controls automatically created by Wezy.
Choose a safe route for each customer
There are two legitimate routes, and they should not be mixed silently:
- A shared reference request is appropriate and accessible. An agent reviews the content and existing JSM sharing, then may enroll that request for voting. An authorized customer can read it and express support.
- The reference request must remain inaccessible. Keep the customer’s conversation private and capture the need for the team’s review. Do not broaden access just to make a voting counter more complete.
The Wezy guide makes the boundary explicit: enrollment does not grant request access. Customers sign in and see eligible requests they can access. Wezy is not a separate anonymous public feedback board.
When the two routes coexist, explain what your demand report includes. Votes on an accessible reference request describe support among eligible participants; they are not a complete census of every private conversation in the service project.
Invite a vote rather than manufacturing one
When an authorized customer can access the reference request, a suggested reply is:
We are reviewing this improvement under the linked request. If you can access it, please check that it describes your need and use the customer-voting panel to express support. Your current support conversation remains the place for account-specific details. A vote helps inform prioritization and does not confirm a delivery date.
If the customer cannot access it, a different reply is more appropriate:
We have recorded the related need for the team’s review. The reference request has a different audience, so we will keep your account-specific discussion here. We will share an appropriate update through this request when a decision is available.
These are communication templates for your team to send when appropriate, not messages sent automatically by Wezy. Do not create a customer vote on someone’s behalf or treat a ticket relationship as their consent to support a proposal.
Keep a trace of duplicate decisions
Use an internal review record to avoid losing the reason for grouping requests:
| Field | Example entry |
|---|---|
| Original request | Internal reference to the customer’s conversation |
| Related problem | Reference request or internal problem identifier |
| Relationship | Same outcome / related / still investigating |
| Visibility checked | Date and owner of the review |
| Customer next step | Invitation to vote, private follow-up or clarification |
| Review outcome | Investigate, keep separate or group for assessment |
Download a blank review CSV. It is a team template, not an import file, an integration or a schema required by Wezy. Store completed copies according to your own access policy.
Before resolving an original request as a duplicate, check your workflow’s consequences for notifications, ownership and customer expectations. Do not promise that votes, watchers, comments or request participants will transfer. The Wezy workflow documented here has no automatic vote-merging step.
Review the consolidated demand without hiding its limits
At the next review, inspect active votes, distinct represented organizations and recent support on the reference request. Read the prioritization framework before interpreting the demand score as the entire decision.
Pay particular attention to two limitations. First, customers with no access cannot express demand on that request. Second, several participants from one organization increase individual votes while that organization is counted once in the organization metric. Neither limitation is an error, but both belong in the explanation of the ranking.
If customer voting on existing JSM requests fits your process, evaluate Wezy on Atlassian Marketplace. Start with the portal-voting setup guide and test visibility before inviting a wider audience.
Frequently asked questions
Does marking a request as a duplicate transfer its Wezy votes?
Do not assume so. The documented Wezy process records votes against eligible requests and does not provide an automatic merge workflow. Review the original voting state and your team’s communication plan before changing or closing requests.
Should every customer see one central feature-request board?
Only if that matches your access policy and chosen tooling. Wezy follows existing JSM request access and does not create an anonymous public catalogue. A shared reference request must be appropriate for its intended audience.
Can we use ticket counts as organization demand?
Ticket volume and represented organizations are different measures. Repeated contacts can come from one organization, while a customer’s vote may be unattributed. Keep those inputs separate so the review does not imply broader organizational support than the evidence shows.
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.