Skip to the guide

JSM workflow guide

Jira Service Management: Feature Request Status Updates

Close the feature-request feedback loop in Jira Service Management with status mappings, customer replies, notification checks and reusable message templates.

Wesy October 26, 2026 7 min read

In short

Turn a feature-request decision into a clear customer reply and portal status, then check recipients separately. A vote records demand; it does not create a delivery commitment or guarantee an email subscription.

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

To close a feature-request feedback loop in Jira Service Management, assign a decision owner, post a customer-visible reply, map the status to the real commitment, and verify the intended recipients. A vote records demand. It does not automatically approve delivery or subscribe every voter to updates.

This guide covers communication after demand review, complementing the prioritization guide. Wezy helps collect and inspect demand; the team owns the decision and its communication.

Atlassian and Wezy documentation checked on October 26, 2026. The scenarios and templates are illustrative, not customer case studies.

Give four decisions an owner

Decision Question to answer Evidence to retain
Demand review What outcome do customers need? Accessible request, current demand and context
Product decision Investigating, committing, deferring or declining? Owner and rationale
Customer communication What can we say accurately? Approved reply and next review point
Audience and notifications Who can see or receive the update? Access and notification checks

“The product team knows about it” is not a customer-facing decision. A popular request may still need investigation, and visibility does not establish email delivery.

Map customer-facing statuses to reality

Atlassian lets teams name portal statuses differently from internal workflow statuses and map several internal states to one customer-facing state. Verify the mapping rather than assuming every internal transition appears as a new external status. Request-type status documentation.

This is an illustrative communication model, not a required workflow or built-in Wezy status list:

Portal state Agreed meaning Avoid implying
Under review The problem is being assessed Work is scheduled
Planned An owner approved a defined scope An unapproved release date
In progress Work on that scope is underway Every requested detail will ship
Available The described capability is accessible to the stated audience An internal deployment reached every customer
Not planned No current delivery commitment Nobody reviewed the request

A vote threshold should not automatically become a delivery commitment. Review scope, feasibility, risk and existing obligations first.

Publish a reply customers can actually read

Open the request as an authorized agent and use Reply to customer for the intended update, rather than leaving the entire decision in an internal note. Atlassian’s customer-update instructions.

Include the problem acknowledged, current decision, practical consequence and next step. Remove confidential estimates, another customer’s details and internal commercial reasoning from a shared reply.

Template: investigating without a delivery promise

We have reviewed the request to [desired outcome]. We are investigating [specific question or constraint]. This is not yet a delivery commitment. We will update this request after [review event or approved date]. Please add relevant details about [bounded question] through the appropriate channel.

Template: available to a defined audience

[Capability] is now available for [supported scope]. Follow [customer-accessible instructions] to use it. This addresses [defined part of the request]; [remaining limitation] is not included. Contact [support route] if the steps do not work for your setup.

Template: not planned at present

We have considered the problem described here. We are not planning the proposed change at this time because [customer-appropriate explanation]. [Existing alternative], where suitable, may address part of the need. We will revisit this if [specific condition] changes.

Replace placeholders with verified information. An arbitrary date does not make a reply more trustworthy.

Check notification recipients separately from voters

JSM notification behavior depends on participation, sharing, roles, preferences and event settings. Atlassian notes that organization-shared customers have notifications off by default until they opt in for that request. A verified reporter or participant follows a different participation path. A Wezy vote alone does not establish either condition. Customer notification behavior.

Customer state Check before promising an email
Reporter or request participant Verified contact, applicable notification and preference
Request visible through organization sharing Request-specific notification opt-in and access
Voter with no confirmed notification relationship Do not assume voting subscribes them
No access to the request Do not broaden sharing merely to send an update

Some events have exceptions to notification preferences. Test the particular event, not a blanket “subscribed” assumption. For failures, review JSM customer notification logs, preferences and delivery settings before blaming the voting app. Atlassian troubleshooting.

This guide does not claim Wezy automatically adds voters as participants, subscribes them to native email or broadcasts releases. Review the permissions checklist before changing the audience.

Worked example: a request is reviewed, not scheduled

Suppose a hypothetical request, DEMO-104, asks for a weekly account report. Several customers support it, but the product owner still needs to confirm which fields are safe to include. The scenario illustrates process; its reference and votes are not real customer data.

A weak response would be “Planned. Thanks for voting.” That turns unresolved investigation into an apparent promise.

A better handoff is:

  1. The agent records the demand and links the internal review for the authorized owner.
  2. The owner decides to investigate the field requirements without committing a delivery date.
  3. The agent checks the portal mapping and leaves the customer-facing state Under review.
  4. The customer reply names the unresolved question and the next review event.
  5. An authorized customer checks visibility; notification recipients are verified independently.

Example reply:

We have reviewed the request for a weekly account report. We are assessing which fields can be included without exposing information outside each account’s access. The request remains under review, not scheduled for delivery. We will update it after that assessment. Please describe any essential fields through your existing support request without posting other customers’ data here.

The useful output is a clear decision boundary and next step, not a higher vote score or an unsupported roadmap date.

Align voting availability with the decision

The Wezy setup guide documents eligibility by request type, open workflow stage, exact status and enrollment. The supported scope is JSM Cloud, company-managed projects. Customers must sign in and have access to the underlying request.

Completed requests cannot accept new votes in this workflow. Recorded votes remain in history; customers who retain access can withdraw them. Removing enrollment does not delete the Jira request or erase Wezy data.

Closing voting, resolving a request and erasing data are different actions. If a request is reopened or rescoped, review eligibility, wording and audience again rather than assuming the old configuration still fits.

Test with customer roles, not only an administrator

Use controlled accounts and a non-sensitive request. These are proposed checks, not completed tests on your site.

Test Observation to record
Authorized customer opens the request Correct portal status and reply visible
Customer without access opens the link No unintended content exposed
Agent adds an internal note It is not the customer-facing update
Agent posts the approved reply Intended audience can read it
Intended recipient expects email Delivery matches the event and configuration
Customer changes notification preference Result checked for the specific event
Request is completed New voting follows documented eligibility
Request is removed from voting No confusion with erasing history or deleting the request

For a failed notification, inspect the documented JSM path. Do not create a mass-recipient list from voting data merely to bypass a permission or subscription question.

Maintain a small decision log

Record the request key, decision owner, decision date, approved message link and next review condition. Store it internally with appropriate access rather than copying sensitive content into a widely shared sheet.

During review, find decisions without an external update and promises whose approved dates have passed. Useful measures include decision-to-update time and the share of decided requests with a clear customer reply. These measures do not by themselves establish revenue impact.

Frequently asked questions

Does a high demand score mean we must build the request?

No. Demand is an input to an owner’s decision about scope, feasibility, risk and commitments. It is not a contract.

Does voting make the request public?

No. Wezy enrollment and attribution do not grant access. JSM sharing remains separate; there is no anonymous public request catalogue.

Does Wezy automatically email everyone who votes?

Do not assume that capability. Use the documented JSM reply and notification process and verify any additional integration before promising a broadcast.

Where should a team start?

Choose one accessible request and validate its decision, portal status, reply and notification path with a customer account. Then apply the process to the next review batch.

Next step: review Wezy Customer Voting on Atlassian Marketplace and the setup guide, then connect demand review to this communication 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.

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