This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.
To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.
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).
The ability to use Forge Dynamic Modules is now available in Preview. These modules are available across Jira, Confluence and JSM. Please see our documentation here for more information.
Thank you to everyone who engaged in our EAP and provided valuable feedback!
We’ve added new APIs to bulk create detail field definitions for both customers and organizations
Refer to API quick start for information on how to get started with the CSM REST API.
Following on from our previous announcement, customer messaging for Marketplace apps is now enabled on tenants enrolled in the Developer Canary Program. This messaging is scoped only to the Connected Apps admin page and in-app messaging will not be available. Only DCP-enrolled tenants are affected, production instances are unchanged.
This gives enrolled partners and developers early visibility into the admin-facing messaging customers will see before it starts to broadly go live in production later, starting 6th July. Please use this window to test and prepare.
The messaging covers:
Connected Apps page: Admins will see a message on installed apps utilising Connect components indicating the platform is approaching end of support and prompting them to check their app. This messaging will change to be app-specific once you have adopted the connectToForgeMigration module and declared your intent to migrate.
What you need to do:
Review the messaging on your canary tenants to understand what your customers will see.
Adopt the connectToForgeMigration module in your Forge manifest to provide app-specific migration guidance directly within the customer-facing notices.
If you are not yet enrolled in DCP and would like to preview, see the https://developer.atlassian.com/cloud/jira/platform/developer-canary-program/.
A changelog notice will be issued at least one week prior to this change going live to production instances
Rollout of this messaging will be staged across 3 months, starting with apps who have not declared any intent to migrate.
The Forge platform will be undergoing maintenance in FedRAMP production on June 7, 2026 between 11am - 12am UTC.
There should be a few minutes of downtime within this window. During this time, the following capabilities will not be intermittently available:
Creating, updating, or deleting apps
Deploying apps
Installing, uninstalling, upgrading apps
App invocations will continue to work for existing users of the apps. However, new customers may be unable to use apps as consent process will be impacted during this interval as well.
Forge custom fields and Forge custom field types are now displayed as columns in Jira's https://support.atlassian.com/jira-software-cloud/docs/what-is-the-list-view/ (New Issue Navigator).
What's new:
Forge custom fields appear as selectable columns in the List View.
When a formatter is defined in your manifest, the List View evaluates and displays the formatted value instead of the raw stored value.
Limitations:
Read-only — Inline editing of Forge custom field values is not available in the List View. Users must open the issue to edit.
No Custom UI / UI Kit rendering — The view.resource component is not rendered; field values are displayed as text only.
Read more here :
We are upgrading from React 18 to 19 in Jira 12, Confluence 11, Bitbucket 11, Bamboo 13, and Crowd 8. React is a core frontend dependency in DC products, and it is also a dependency for other important frontend libraries such as Atlaskit.
The goal of this work is to keep DC products secure and compliant with our dependency policy, while also making it possible to continue upgrading other critical frontend dependencies in the future. Because of this, Marketplace apps using React will also need to upgrade to React 19.
Areas affected by this upgrade:
com.atlassian.plugins:react web resource will now provide React 19
Clienside Extensions (CSE) will now use React 19
We encourage all app developers to use the shared platform web resource (com.atlassian.plugins:react) where possible, as it helps reduce bundle size and address security issues quickly with platform-wide patch rollouts.
As we learn more and develop tools to help with the migration, we will share our findings on the developer documentation.
If you have any comments, feel free to leave your feedback on the developer community announcement.
We’ve added a new experimental API to fetch entitlements in a paginated form.
Refer to API quick start for information on how to get started with the CSM REST API.
Forge apps using the UI Modifications API configured for Issue View will now have their modifications applied when issues are opened via ViewIssueModal (for example, from global pages, admin pages, or custom UI panels).
Previously, UI Modifications were not loaded silently in this context. This applies to all supported project types, and requires no changes to your app's manifest or code
For more details, see the Jira UI modifications documentation.
The Developer Console’s invocation error metrics and alerts screen now features a new Missing scopes error type for Product Events and Agent Connector invocations. This makes it easier to identify and troubleshoot invocation errors caused by insufficient permissions, which frequently occur during app-to-app validation.
You can now:
View Missing scopes as a distinct category in the Invocation errors chart.
Use Missing scopes as a filter when creating Advanced alerts to stay informed about permission-related failures.
What you need to do
No action is required to enable this feature. If your app experiences invocation failures due to missing scopes, they will now be automatically categorized and surfaced in the Developer Console.
Forge embedded macros have reached general availability (GA). This feature allows Forge bodied macro apps to render other embedded Forge macro apps, enabling more complex and integrated content experiences within Confluence.
What’s changing
You can now use the following methods to render embedded Forge macro apps within a bodied macro:
UI Kit: Use the AdfRenderer component.
Custom UI: Use the view.createAdfRendererIframeProps method from the @forge/bridge package.
What you need to do
To start using embedded macros in your bodied macro apps:
Ensure you are using the latest version of @forge/bridge for Custom UI apps.
Implement the AdfRenderer (UI Kit) or createAdfRendererIframeProps (Custom UI) in your macro's rendering logic.
Refer to the updated Forge rich-text bodied macros documentation for implementation details and examples.
As part of the ongoing Marketplace platform re-architecture, all Marketplace V2 APIs will be permanently switched off on June 30, 2026.
What does this mean?
Every endpoint under /rest/2/ is affected — this is a complete sunset of the V2 API surface, not a partial deprecation.
No V2 APIs will continue to function beyond June 30, 2026.
June 30 is a hard removal date — after this date, any V2 API calls will return errors.
Note: Some V2 endpoints were marked deprecated on DAC earlier and have already completed their 6-month deprecation window. All remaining V2 endpoints are completing their deprecation window on June 30, 2026. Regardless of whether a specific endpoint has an individual deprecation marker on DAC today, it falls under this blanket sunset and will stop working.
What should you do now?
Audit all your integrations for any calls to /rest/2/ endpoints
Identify the V3 equivalents using the The Atlassian Marketplace REST API
Complete your migration to V3 before June 30, 2026
Test your V3 integrations in production — V3 APIs are live and available today
Resources:
Full context on what's changing and timelines: Marketplace Platform Changes GA and Partner Implications - Quick Reference Guide
Specs and contracts for replacement APIs: The Atlassian Marketplace REST API
Official deprecation notice: Marketplace changelog
Need help?
If you can't find a V3 equivalent for a V2 endpoint you rely on, please reach out to us here so we can assist with your migration path.
Forge LLM is now officially in Preview. This transition makes Forge LLM available to all developers as a billable capability.
What’s changing
Progressive Rollout: We are using a progressive rollout strategy to enable Preview access. This means it may take a few days for the necessary feature flags to reach all tenants.
Temporary Error Messages: During this rollout period, you may still see an error message stating: Forge LLM feature is available exclusively in the Development environment through the EAP program. This message will persist until the rollout is complete for your specific environment.
Billing: All Forge LLM usage is now billable. Please ensure your apps are associated with a developer space that has active billing details.
Model Deprecations: The following older model versions are now deprecated and are not included in the Preview release:
claude-sonnet-4-20250514
claude-opus-4-1-20250805
claude-opus-4-5-20251101
What you need to do
Review the Forge LLMs pricing to understand how credits and billing work.
Update your app configurations to use supported model versions.
Verify your billing details in the developer console to ensure uninterrupted service.
For technical implementation details, refer to the Forge LLMs API reference.
What’s changing:
The Confluence Cloud REST API v2 endpoints for listing page and blogpost versions now enforce a maximum limit of 50 results when the body-format query parameter is included. Requests without a body-format parameter are unaffected.
Affected endpoints:
• GET /wiki/api/v2/pages/{id}/versions
• GET /wiki/api/v2/blogposts/{id}/versions
Previously, requests with body-format could return up to 250 results. If the requested limit exceeded the maximum, the API returned a 400 Bad Request error.
With this change, if the requested limit exceeds 50 when body-format is specified, the response will be capped at 50 results and return 200 OK.
What you need to do:
If your integration relies on receiving more than 50 versions in a single request with a specific body format, you must update your logic to handle pagination. Use the cursor provided in the _links.next field of the response to fetch subsequent pages of results.
Rate this page: