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.

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!

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

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.

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:

  1. claude-sonnet-4-20250514

  2. claude-opus-4-1-20250805

  3. claude-opus-4-5-20251101

What you need to do

1. Review the Forge LLMs pricing to understand how credits and billing work.

2. Update your app configurations to use supported model versions.

3. Verify your billing details in the developer console to ensure uninterrupted service.

4. For technical implementation details, refer to the Forge LLMs API reference.

We're releasing multi-entry resource bundles for Forge apps into preview. This update allows you to group multiple named entry points within a single resource, helping you optimise app performance and stay within resource limits.

What's changing
Previously, apps with multiple modules required a separate top-level resource entry in manifest.yml for each view, consuming one bundle slot per module. You can now define multiple named entry points within a single resource using the new entry property.

You can reference each entry from any module using slash syntax: resource: <resource-key>/<entry-key>. This feature is available for both UI Kit and Custom UI apps.

Why this matters

• Lower bundle count usage: Multiple entries within one resource count as a single resource against the 50-resource limit.

• Smaller deploy size and faster load times: For UI Kit, the Forge CLI automatically extracts shared dependencies into common chunks. For Custom UI, you can achieve similar benefits by configuring code splitting in your build pipeline (e.g., via webpack or vite).

• Fully backwards-compatible: Existing apps require no changes. The entry property is optional, and resources without it behave as before.

Key details

• Maximum of 50 entries per resource.

• Entry values must be flat filenames directly within the path directory; nested paths (e.g., views/global.jsx) are not supported.

• As a Preview feature, this is considered stable but remains under active development and may have shorter deprecation windows.

What you need to do
To get started, review the updated resources manifest reference for documentation and examples.

As recently announced in Raising the bar on Marketplace cloud app security: together we are updating the Marketplace Security Bug Fix Policy to shorten vulnerability remediation timelines for Marketplace cloud apps. These changes ensure a higher security standard across our ecosystem.

What’s changing
The remediation Service Level Objectives (SLOs) for Marketplace cloud apps are being shortened. The timelines for Data Center apps remain unchanged.

Updated Cloud App SLOs (Enforceable September 1, 2026):

• Critical: 10 days

• High: 4 weeks

• Medium: 12 weeks

• Low: 25 weeks

Data Center App SLOs (Unchanged):

• Critical: 12 weeks

• High: 12 weeks

• Medium: 12 weeks

• Low: 25 weeks

Additionally, we have published the Marketplace Security Enforcement Policy, a consolidated source of truth for marketplace security compliance expectations, including vulnerability management, OAuth compliance, partner verification, bug bounty participation, and incident response.

What you need to do

• Review the new timelines: Ensure your internal processes are updated to meet the new cloud app SLOs by September 1, 2026.

• Check your tickets: We have corrected an issue where some AMS Data Center tickets incorrectly showed cloud remediation dates. If you believe a ticket still has an incorrect date, please raise an ECOHELP ticket.

• Watch the policy page: The Marketplace Security Enforcement Policy is a living document, we recommend "watching" the page for future updates.

We are introducing rate limits for Forge Realtime to ensure the stability and reliability of the service for all apps.

What’s changing
Starting June 26, 2026, a rate limit of 50 requests per app installation per second will be enforced for Forge Realtime. For more information, see our rate limit documentation.

Based on our current telemetry, no existing Forge apps exceed this limit, so we do not expect any immediate impact on your app's performance. This change is a proactive measure to maintain service health.

What you need to do

• Review your app's use of the Realtime Events API and Bridge API Realtime method to ensure your request frequency remains within the new limit.

• If you anticipate needing a higher rate limit for a specific use case, please reach out via the developer support portal.

As Connect approaches end of support in December 2026, we are starting to roll out customer messaging in the admin experience to inform admins when an installed app runs on a soon to be unsupported platform, Connect. Following on from our previous announcement, this messaging will gradually rollout over the next week to be live in production for non-public apps only and is scoped to the admin experience, end users will not see any notices at this stage.

On Jun 2, 2026, we will enable customer messaging on Developer Canary tenants for public apps. This will include notices in admin facing experiences so enrolled partners can preview the exact messaging their customers will see and have the chance to adopt the new connectToForgeMigration module in their manifest before it goes live in production.