Atlassian developer changelog

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:queuePage with customerServiceManagement:queuePage in your app's manifest.yml.

• Review the manifest reference for the new module.

• Deploy your changes before the deadline.

Timeline

• 15 June 2026: customerServiceManagement:queuePage reaches GA.

• 15 June 2026 – 14 September 2026: Migration window.

• 15 September 2026: jiraServiceManagement:queuePage stops loading on CSM spaces.

If you cannot migrate in time, please contact Atlassian for case-by-case support.

The app migration platform will now automatically detect the correct migration listener to invoke if multiple are defined. This can be useful for defining different migration paths to different environments (i.e. commercial, isolated cloud and AGC) or if you would like to support migrations to one or more cloud apps.

To find out more, our documentation is available here

The new customerServiceManagement:queuePage Forge module is generally available from 15 June 2026.

What's changing

This module lets you add a custom item under the Queues section in the left navigation of a Customer Service Management (CSM) space. When clicked, your app renders a full page within the Jira interface.

What you need to do

• Review the customerServiceManagement:queuePage manifest reference for configuration details.

• If you currently use jiraServiceManagement:queuePage on CSM spaces, you must migrate to this new dedicated extension point.

Related deprecation

As a result of this new dedicated extension point, the existing jiraServiceManagement:queuePage Forge extension point will no longer load on CSM spaces from 15 September 2026. See CHANGE-3175 for migration details.

The new customerServiceManagement:requestDetail Forge module is generally available from 15 June 2026.

What's changing

This module lets you add a panel to the request details screen of a Customer Service Management (CSM) support site. Your app's content is displayed below the Conversation history section on the request details page.

What you need to do

Refer to the customerServiceManagement:requestDetail manifest reference for technical configuration and schema details.

The new design language updates for IconTile — previewed at Team '26 and previously rolling out behind feature flags — are now the default in @atlaskit/icon v35.0.0.

Alongside the feature flag cleanup, there are API changes you'll need to be aware of.

The size prop on IconTile no longer accepts pixel number strings. All sizes now use t-shirt size names. The following pixel values have been removed and must be migrated:

The default size has also changed from "small" (24px) to "medium" (32px). If you were relying on the default, explicitly pass size="small" to retain the previous behaviour.

A new "xsmall" size has been introduced, rendering at 20px. This is now the smallest available IconTile size.

The size="16" option for IconTile has been removed entirely as it was too small to be accessible. There is no 16px tile — the smallest tile is now "xsmall" at 20px.

If you previously used a 16px IconTile, migrate to rendering the 16px icon directly with a colour token:

The transitional types LegacyIconTileSize and NewIconTileSize have been removed. Use IconTileSize directly:

IconTileSize is now the single canonical type, defined as:

The shape prop on IconTile has been deprecated for over 6 months now and will be removed in a future version very soon. Circular icon tiles will not be supported.

If you are currently using shape="circle", you must plan your migration now:

• Assess the need for circular icon appearance: We’re asking you to migrate to square Icon tiles where possible, otherwise

• Use ADS primitives: Rebuild using ADS primitives (Box with borderRadius: radius.full for example).

The IconTile component is coming soon to Forge UI Kit.

• IconTile documentation on atlassian.design

Forge apps can now make API calls on behalf of JSM portal-only users. JSM portal-only users (also called customer account users) are customers who access your service desk through the JSM portal but don't have a full Atlassian account.

With this release, asUser() in Forge now works for customer accounts from both the frontend and the backend.

Apps can now perform actions like creating customer requests, reading comments, and updating tickets in the context of the portal-only user, with full permission checks preserved, exactly as they would be for a standard Atlassian account user.

The changes will be reflected upon redeployment of the Forge app.

What's changing

Forge custom fields (FCF) of type object can now render a rich custom edit experience in Jira's bulk edit.

Previously, object type FCF were rendered as an empty text input via (Atlaskit's TextField). With this change,

• It will be rendered as an empty JSON schema, making it easier to inline edit.

• You can now control how the field renders during bulk edit using your own custom resources via UI Kit or Custom UI, consistent with other surfaces such as issue view and global issue create.

This is available as a Preview feature, and currently only for the object field type.

What you need to do

• To opt in to the bulk edit experience, add issue-bulk-edit to the edit experiences of your custom field (or custom field type) in your manifest.yml:

  1 2 3 4 5 6 7 8 9 10 modules: jira:customField: - key: my-object-field name: My object field type: object edit: experience: - issue-create - issue-transition - issue-bulk-edit // <-- new surface

• Keep these constraints in mind for the bulk edit experience:

  • Issue and Project details are not available in the extension context during issue-bulk-edit.

  • In the formatter expression, only value and fieldId are available when renderContext/experience is issue-bulk-edit.

  • If your edit UI depends on issue or project context, detect this case using renderContext === 'issue-bulk-edit' and render an appropriate fallback UI.

For details, see: Jira Custom Fields > Issue Bulk Edit.

We've added a new set of public REST API endpoints that let you migrate Confluence spaces from the legacy granular space permission model to role-based access control (RBAC) using space roles.

Confluence spaces historically used 14 granular permissions (e.g. Add page, Delete attachment, Set permissions) assigned directly to users and groups. This checkbox-based model is difficult to audit, bulk-manage, and keep consistent across hundreds of spaces.

Confluence is replacing this with role-based access control (RBAC), where each principal (user, group, or app) is assigned a single space role (e.g. Admin, Collaborator, Viewer) that bundles the relevant permissions together.

These endpoints are the programmatic migration path: they let Confluence admins convert existing granular permission grants into equivalent role assignments — in bulk, without manual remapping — and are designed to be called from scripts or admin tooling.

All endpoints are under /wiki/api/v2/space-permissions/transition:

• GET /combinations — List a space's permission combinations that don't yet map to a role

• POST /combinations — Generate the permission combinations for a space

• POST /role-assignments — Bulk assign space roles to users/groups based on their existing permission combinations

• POST /access-removals — Bulk remove legacy permission combinations after transitioning to roles

• GET /tasks/{taskId} — Check the status of a transition task

• read:configuration:confluence — for the GET endpoints

• write:configuration:confluence — for the POST endpoints

Calling these endpoints requires Confluence site admin permission.

1. POST /combinations — compute the permission combinations currently in use across a space's grantees (returns a taskId)

2. Poll GET /tasks/{taskId} until COMPLETED

3. GET /combinations — list the combinations that aren't yet mapped to an RBAC role

4. POST /role-assignments — bulk assign roles so existing users and groups retain equivalent access under the new model

5. POST /access-removals — bulk remove the legacy permission grants that have been superseded by role assignments

6. Poll GET /tasks/{taskId} for the assignment / removal tasks until COMPLETED

These endpoints are experimental. We're validating the API contract against real-world migration workloads and plan to stabilize it once we've confirmed the shape holds across a range of tenant configurations.

Available now in all Confluence Cloud editions in roles transition mode. Please raise issues on the Atlassian Developer Community if you find anything.

We’ve added new navigation targets for the Forge bridge’s router object. These allow you to use the router API to navigate to supported UI module pages in Bitbucket.

What’s changing:

The following Bitbucket modules are now supported as navigation targets:

• bitbucket:workspaceGlobalPage

• bitbucket:workspacePersonalSettingsPage

• bitbucket:workspaceSettingsMenuPage

• bitbucket:projectSettingsMenuPage

• bitbucket:repoMainMenuPage

• bitbucket:repoSettingsMenuPage

What you need to do:

You can now update your Custom UI or UI Kit apps to use these targets with router methods. For implementation details and examples, see the router object documentation.

What's changing
We've added new error handling documentation for Forge Realtime. This covers expected error patterns and recommended handling strategies for all realtime operations:

• publish

• subscribe

• signRealtimeToken

The new guidance includes details on:

• Rate limit errors: How to identify and respond when your app exceeds Realtime service limits.

• Token pre-validation errors: Troubleshooting issues during the token signing and validation process.

• Common failures: A catalog of other frequent error scenarios with actionable recovery steps.

What you need to do
Review the new https://developer.atlassian.com/platform/forge/realtime/error-handling-for-realtime-methods/ documentation to ensure your app gracefully handles these scenarios. We recommend implementing the suggested retry logic and validation checks to improve your app's reliability.

Bitbucket Data Center and Server 9.4.21 and 10.2.4 bug fix releases are available now!

To see the issues resolved in these bug fix releases, go to:

• Bitbucket Data Center 9.4 release notes

• Bitbucket Data Center 10.2 release notes

Get the latest LTS bug fix release

A new Rovo-powered AI chat widget is now available for all logged-in users on https://developer.atlassian.com. Located in the bottom right corner of developer documentation pages, this assistant can answer questions, surface relevant docs, and help you build on the platform faster.

Key features include:

• Contextual answers: The chat understands the context of your question and provides relevant answers rather than generic search results.

• Developer-focused knowledge: Trained on Atlassian developer documentation, the assistant understands Forge, REST APIs, Marketplace, and platform concepts.

• Natural language understanding: Ask questions in plain language; no need to know exact documentation titles or keywords.

• Follow-up questions: Continue a conversation naturally with follow-up questions to drill deeper into a topic.

• Source transparency: The widget displays the specific documentation and support sources used to generate each answer.

• Conversation history: You can access and review your previous interactions for up to 28 days.

• Independent operation: The assistant works independently of your product licenses and organization-level AI settings.

For more details on how the assistant handles data and what sources it uses, see the Atlassian developer AI chat documentation.

You can now use Jira entity properties (issue, project, and user) to filter Forge trigger events and include them in the delivered event payload. This allows your app to process only relevant changes and reduces unnecessary executions.

What’s changing

• Entity property filtering: You can now define expressions in your manifest.yml that use Jira entity properties to filter events before they trigger your app.

• Payload enrichment: Relevant entity properties can now be included directly in the event payload, eliminating the need for additional REST API calls to fetch this data.

What you need to do

• Update your manifest.yml to include expression filters using entity properties.

• Update your event handlers to utilize the enriched payload data.

• For more information, see the Forge Trigger module reference.

Customer-managed egress and remotes in Forge is now available in Preview. This feature enables apps to dynamically declare egress and remotes post-installation, giving site administrators control over where apps can send and receive data.

Apps using customer-managed egress and remotes can now be used in production environments.

We are upgrading the design tokens to version 13.0.4 in all our upcoming DC product releases, including LTS versions.

The design tokens apply the visual foundations in Atlassian app experiences. This upgrade will result in a minor change in the visual style of affected products, especially icon colors, borders colors, and accent colors.

The main reason for this upgrade is to retain forward compatibility and consistency with newer versions of Atlaskit components.

Target releases:

• Bamboo 12.1.8

• Bitbucket 11.0.0 (10.2.0 provided the latest tokens to match Cloud; 11.0.0 removes the override and falls back to AUI)

• Confluence 10.2.14

• Confluence 11.0.0

• Crowd 7.2.1

• Jira 11.3.7

This change is delivered via AUI 10.2.0 (changelog).