JSM release impact and audit checklist
JSM Portal UI Modifications: Forge Scope Deadline, December 2026
Atlassian announced new JSM-specific Forge scopes on November 16. Check request-create portal extensions before December 15 without confusing them with customer voting.
In short
Atlassian's December 15, 2026 Forge scope deadline applies to UI Modifications on JSM portal request-create forms. First identify whether your extension uses that module; don't assume an existing request voting panel is affected.
In this guide
Atlassian announced on November 16, 2026 that Forge apps using the jira:uiModifications module on Jira Service Management portal request-create forms must declare JSM-specific scopes by December 15, 2026. If you manage such a portal extension, review its manifest, deploy the required scopes and complete any necessary installation upgrades before the deadline. This is not a blanket warning that all JSM apps or customer voting experiences will stop working.
The official JSM Cloud developer changelog is the source for both dates and the scope sets. This guide is aimed at JSM administrators, integrators and Forge app maintainers who operate a request-creation experience alongside customer feedback.
Start with the affected surface, not the app name
Atlassian describes a narrow technical scope: UI Modifications running on the JSM portal request-create form. An existing-request portal panel, an agent issue panel, a Jira Automation rule or a customer voting dashboard is not automatically that module simply because it appears somewhere in Jira Service Management.
| Surface or behavior | Initial relevance to this announcement |
|---|---|
| Forge jira:uiModifications on JSM portal request-create form | In scope; audit before December 15 |
| Same Forge app also extending Jira issue create or issue view | May need to retain Jira-specific scopes as well |
| Portal request-detail experience after creation | Do not infer this module is used; inspect implementation |
| Native JSM workflow/request type field | Not enough evidence of this Forge UI module |
| Wezy customer voting on enrolled, existing requests | No automatic conclusion; check the actual app modules and published documentation |
This distinction protects against an expensive mistake: widening permissions for every installed app without first confirming that the affected Forge module is actually present.
What Atlassian requires
The November 16 announcement gives two alternative complete sets, not a list to pick individual permissions from:
| Option | Scope set (verify directly in Atlassian docs) |
|---|---|
| Classic | read:servicedesk-request; write:servicedesk-request |
| Granular | read:servicedesk:jira-service-management; read:requesttype:jira-service-management; read:request:jira-service-management; write:request:jira-service-management; read:user:jira |
Atlassian says choose the entire classic set OR the entire granular set, merge it into the Forge manifest and redeploy. The corresponding installation may need an upgrade when scopes change. If the app also supports Jira views, do not delete their required Jira scopes as part of a cleanup. Beginning December 15, 2026, JSM portal request-create UI Modifications without the required complete JSM scope set will no longer execute.
Source: Jira Service Management Cloud changelog, November 16, 2026. This is a future enforcement deadline as of the article’s November 16 publication date, not evidence of an outage today.
A safe audit plan for a Jira administrator
A customer-facing portal can combine native request forms, Forge extensions and separate apps. Ask each extension owner to complete this proposed checklist:
- List Forge apps extending portal request creation and identify the exact module and deployed environment/version. Do not infer the module from a screenshot.
- For each affected app, have its maintainer review manifest permissions against the official change; administrators should not guess or patch a vendor’s code.
- Confirm whether a new deployed app version and an installation upgrade are required for the added scopes.
- Test request creation as an authorized customer and verify the intended modified fields or controls appear.
- Test a denied or unauthorized customer path to ensure permission changes have not widened request access.
- Submit a synthetic request and validate the downstream native workflow, approval and notification behavior.
- Retest existing-request tools—such as customer voting—separately so a success on one page is not reported as success for another.
The steps are proposed, not tests run against Wezy or an Atlassian tenant. Keep an evidence sheet with pass, fail and not tested for each account role and portal page. When an external app needs a scope update, contact its developer rather than broadening permissions across your Jira site.
Where Wezy customer voting belongs in the journey
Wezy Customer Voting for Jira Service Management is documented for JSM Cloud company-managed projects. An agent enrolls a reviewed, appropriately shared existing request, and signed-in customers with existing JSM access can vote on it. The current setup guide explains request types, statuses, portal voting and agent demand dashboards.
That workflow is conceptually different from modifying fields while a customer creates a new request. The public Wezy documentation does not establish that the app uses the affected jira:uiModifications request-create module, so this article does not claim that Wezy requires a scope migration. The app’s maintainers must inspect the actual deployed manifest to determine that fact. Likewise, this article cannot guarantee that every third-party installed app is unaffected.
If a team’s new request form fails but previously enrolled request voting works, investigate the form extension independently. If voting fails after a workflow/status change, follow the voting regression checklist; do not automatically attribute it to the December scope announcement.
A boundary test with two customer journeys
Choose two synthetic requests and separate accounts for an authorized customer, an unauthorized customer and an agent. These are example acceptance conditions, not observations from production.
| Test journey | Expected evidence |
|---|---|
| Authorized customer opens portal create form | Required request fields and any documented UI Modifications display |
| Authorized customer submits a new request | Native JSM request is created as expected |
| Unauthorized customer tries restricted request type | Existing access boundary remains intact |
| Agent reviews the newly created request | Agent can choose whether it is suitable for enrollment; no automatic enrollment assumed |
| Signed-in authorized customer opens an already enrolled request | Wezy voting appears only where its own saved rules and native sharing allow it |
| Customer without access opens the enrolled request URL | No request/voting-content disclosure via Wezy |
| UI Modifications scope upgrade is not yet installed | Mark not tested or blocked; do not call a preview an upgraded tenant |
A successful request submission is not proof that customer voting is working, and a successful vote is not proof that the request-create Forge extension has migrated.
Prepare for the deadline without changing unrelated app permissions
For an affected maintained Forge extension, use a dated owner checklist:
| By when | Owner action | Evidence to keep |
|---|---|---|
| During November | Identify affected request-create modules and their environment | Module inventory, current manifest reference |
| Before December 15 | Choose a complete classic or granular JSM scope set; preserve Jira view scopes when needed | Reviewed manifest diff and deployment version |
| Before December 15 | Complete any required app installation upgrade | Installation record and access approval |
| Before December 15 | Exercise permitted and denied portal create flows | Role-by-role pass/fail/not-tested sheet |
| After rollout | Monitor actual request-create error reports | Incident owner and rollback procedure |
The deadline is Atlassian’s; this timetable is a suggested implementation plan, not an Atlassian-mandated migration calendar or evidence that Wezy uses this module. Request an explicit update from a third-party vendor when the manifest is not under your control.
Record a narrow rollout decision
For affected in-house Forge extensions, document the selected scope option, manifest diff, deployed version, installation upgrade state, test account role, observed portal output and rollback owner. For third-party extensions, record the vendor’s published update and the local installation state. Avoid storing customer request content in a shared public checklist.
If no installed or maintained extension uses the named module on the named surface, this announcement may require no change to that team’s setup. Keep the decision and the evidence of scope review; do not publish a misleading site-wide incident banner.
Next step: read Atlassian’s November 16 developer announcement, inventory affected request-create extensions, and use the Wezy customer voting guide only for the distinct existing-request voting journey. Evaluate Wezy on the Atlassian Marketplace if you need customer demand signals rather than request-form modifications.
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.