Atlassian developer changelog

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).

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

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 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 :

• https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#list-view

• https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type/#list-view

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.

1. Extend Rate-limit to all endpoints: Apply rate limiting consistently across all APIs and UI endpoints to ensure uniform protection. This prevents abuse or traffic spikes from targeting unprotected endpoints. It also improves overall system stability and fairness in resource usage.

2. Rate Limiting Configuration Options for Bot and User Requests: Provide configurable rate limits separately for automation traffic and user requests. This allows stricter control over automated traffic while preserving user experience. It also enables flexibility for different customer environments and usage patterns.

3. Global Error Handling for “Too Many Requests” (HTTP 429): Introduce a centralized mechanism to handle HTTP 429 responses across the application. Ensure consistent error messages are returned to clients. This improves client experience

These are the new V2 endpoints created to support dual configuration in the backend.

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.