When the phased enforcement begins, API requests then start consuming points based on the work they perform, such as the data (objects) returned or operations triggered. Each request starts at a base point of 1 point, with additional points for each object involved.

We’re also introducing two types of app-level quotas (tiers) that apply consistently across the Atlassian platform for all apps.

It’s important to note that the vast majority of free and paid apps do not require any changes and are already operating within these limits. We’ve also reviewed usage and upgraded eligible apps to a higher tier where appropriate.

If your app requires additional capacity in the future, rest assured we will provide clear pathways to request for this. For more information, please refer to the following documentation:

• Jira Cloud Platform Rate Limits

• Confluence Cloud Rate Limits

Following the Preview release, the Forge Automation Actions is now generally available. The Automation action module allows you to extend the Automation Platform and add new Forge-based actions to your app. With this release Forge Actions can now output smart values, enabling seamless data flow and dynamic automation.

For more information, see the Forge Automation Action module documentation.

We've added a new optional hidden property to the Forge macro module. When you set "hidden": true in your macro definition, the macro will be hidden from the quick insert menu and macro browser. This prevents users from searching for and inserting the macro into new pages, but existing macros will continue to render as usual.

For more information, see Macro.

You can now configure the Forge Content Byline Item module to open in a modal instead of a pop-up. The modal supports both standard and full-screen sizes, giving you more flexibility in how your content is displayed. This can be done by using viewportContainer: modal in your manifest.

Forge platform will be undergoing maintenance in commercial production on November 23, 2025 for approximately 1 minute between 5:30-6:30am UTC

During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

Following our prior deprecation notice, requests to the following internal API endpoints will now fail.

• /download/attachments/{id}/crash-scraper/files/{id}

• /download/attachments/{id}/{id}/customer-card-payment-rest

• /download/attachments/{id}/{id}

• /download/attachments/{id}/{id}/{id}

• /download/download/attachments/{id}/{id}

• /download/attachments/{id}/{id}/{id}/{id}

• /download/attachments/{id}/attachments/{id}/{id}/{id}

• /download/attachments/{id}/{id}/image

• /download/all_attachments

The sidebar will now span the full height of your Atlassian app, making it easier to find and interact with. Starting late November 2025, this update will roll out to all customers who haven’t customized the look and feel of their sites. This change won’t affect the width and height of your Forge and Connect apps.

Along with this, we’re introducing a few improvements to sidebar interactions:

• Double-click to collapse: When expanded, double-click the button to quickly collapse the sidebar.

• Global shortcut: Use Ctrl + [ to expand or collapse the sidebar at any time.

• Helpful tooltips: Tooltips will appear to guide you through the interaction.

For sites with customized look and feel, the full-height sidebar can disrupt intentional design choices, such as:

• Custom logos and titles

• Favicons

• Navigation colors

• Dark and light mode settings

Because of this, the sites with customized look and feel won’t receive the update just yet.

For the sites without customized look and feel, we’re opening up the opportunity on Nov 21, 2025 to let you use this feature early and test it with your apps. If you’re interested, please sign up here with your site details.

As part of our new design language, the refreshed colors and components in the Atlassian Design System (that first launched in products at Team '25) are now officially in GA. Also included is a further tweak to accent token colors in hover/pressed states to improve accessibility.

What you need to do if you are using Forge Custom UI or Atlassian Connect:
Bump @atlaskit/tokens + relevant component packages to the latest version to align your app's look and feel with Atlassian apps.
What you need to do if you are using Forge UI Kit or Forge UI Kit 2:
Nothing! You should have the newest components by default.

The GET methods of the Key-Value Store and Custom Entity Store SDKs can now return optional metadata fields, namely:

• createdAt

• updatedAt

The ability to build Forge apps that are compatible with multiple Atlassian apps is now available in Preview. This feature allows you to declare compatibility in your app’s manifest and enables your app to be installed and used across Jira, Confluence, and Compass.

For more information, see App compatibility.

We’ve added new Confluence Forge events for relations:

• avi:confluence:created:relation

• avi:confluence:deleted:relation

You can use these events to invoke your Forge app function when a relationship is created or deleted in Confluence. For more details, see the Confluence events reference documentation.

Following our prior deprecation notice, the following internal API endpoints will now result in a 404 Not Found response.

• /wiki/rest/masterdetail/1.0/detailssummary/lines

• /download/thumbnails/{id}/{id}

• /download/resources/{id}/icons/{id}

• /download/resources/{id}/{id}

• /download/resources/{id}/images/{id}

The following UI Kit Editor components are now available through Forge’s Early Access Program (EAP). To join, please complete this sign-up form.

• Chromeless editor

• Comment editor

These components are available in Confluence and Jira modules.

When defining resolvers, the front-end code can share the types with the backend so the invocation interface is type-safe. This helps catch potential errors during compilation.

The following Confluence display conditions are now generally available:

• entityPropertyContainsAnyUserGroup

• hasPagePermission

• hasSpacePermission

• userIsExternalCollaborator

• Confluence Entity Property conditions now also support app and user properties

Learn more about these conditions here.