Deprecation: jiraServiceManagement:queuePage will no longer load on CSM spaces
- Announced
- Effective
- Sunset
- APIs
- forge-jsm-cloud
- Severity
- breaking, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3175
On 15 September 2026, the jiraServiceManagement:queuePage Forge extension point will stop loading on Customer Service Management (CSM) spaces in Jira.
What's changing
Apps using this module on CSM queues will stop rendering on that surface from the deprecation date. The module will continue to function as expected on standard Jira Service Management (JSM) spaces.
What you need to do
You should migrate to the dedicated replacement extension point, customerServiceManagement:queuePage, which is generally available from 15 June 2026.
- Replace
jiraServiceManagement:queuePagewithcustomerServiceManagement:queuePagein your app'smanifest.yml. - Review the manifest reference for the new module.
- Deploy your changes before the deadline.
Timeline
- 15 June 2026:
customerServiceManagement:queuePagereaches GA. - 15 June 2026 – 14 September 2026: Migration window.
- 15 September 2026:
jiraServiceManagement:queuePagestops loading on CSM spaces.
If you cannot migrate in time, please contact Atlassian for case-by-case support.
More details: [object Object]
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.