Action required: Update Jira UI Modifications manifest for anonymous user support
- Announced
- APIs
- forge-jira-cloud-platform, forge-jsw-cloud
- Severity
- info, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3302
What’s changing?
We’re enhancing the jira:uiModifications module to support interactions with different user types in Jira.
Apps with UI Modifications that need to work for anonymous users must explicitly declare this in the app manifest using the unlicensedAccess attribute.
This change will take effect on 2026-06-29. We recommend that you deploy an update to your app before this date to avoid any interruption to your app’s functionality for anonymous users.
What you need to do
Add the anonymous value to the unlicensedAccess attribute for each jira:uiModificationsmodule that needs to execute for anonymous users in Jira.
jira:uiModifications:
- key: your-app-key
title: Your UI Modification
resource: yourResource
unlicensedAccess:
- anonymous
For more information, see the guide on Access to Forge apps for unlicensed users.
What happens if you don’t update?
From Monday 2026-06-29 onwards, UI Modifications modules will not be executed for anonymous users unless the module explicitly declares it.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.