Following a recent incident (see details), we have temporarily paused automatic Connect to Forge migrations. Our team is actively working to enhance system robustness and prevent similar issues from occurring in the future.

Once these improvements are complete, we will re-enable and resume the migration process.

We're updating the cursor behavior in the Storage Remote GraphQL API for both Key-Value Store (KVS) and Custom Entity stores. Currently, KVS returns individual cursors for every edge, while Custom Entity edge cursors always point to the last element of the current page. To reduce confusion and align with the new REST API, both stores will now return a single cursor at the end of each page.

This change will take effect after March 20, 2026.

Following our prior deprecation notice, you can no longer publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace.

From now on, all Atlassian Marketplace apps should be built using Atlassian’s Forge platform.

Forge platform will be undergoing maintenance:

• in FedRAMP production on September 21, 2025 between 5-6am UTC

• in commercial production on September 28, 2025 between 5-6am 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.

Macro Autoconvert has be updated to allow custom URL schemes to be used as matchers for URLs. See the Macro Autoconvert docs https://developer.atlassian.com/platform/forge/manifest-reference/modules/macro/#macro-autoconvert

Forge now supports migrating custom content modules from Connect to Forge while preserving existing content. Add the migratedFromConnect: true to your custom content module to maintain compatibility with existing Connect content.

See the documentation for more details.

Forge offline user impersonation was recently made available in Preview. As part of this, the ability to exchange a Forge system OAuth token on a Forge remote for a token to impersonate any user.

This was released with a rate limit of 10,000 requests per minute per app, however after carefully consideration, we need to temporarily reduce this limit to 1,000 requests per minute per app. This rate limit applies only to the exchanging of a system token for a user impersonation token using the offlineUserAuthToken GraphQL mutation. Calls from a Forge function using asUser are not affected. Calls made to APIs using these tokens are not affected and instead use the rate limit defined for each API endpoint

We will continue to work towards increasing this limit as we move towards general availability of this feature.

When an app moves from Connect to Forge today, developers can opt-in to automatically roll out the Forge version to existing Connect customers. Following the introduction of Forge bulk-upgrades, from Aug 18, 2025 the first update from Connect to Forge will now automatically rollout to customers when an app is eligible. Rollouts will now also occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.

Apps which have already moved from Connect to Forge and have not opted in for this behaviour will see customers progressively updated if their latest Forge version is eligible from Aug 18, 2025.

We are announcing support for the following Connect on Forge Jira Software provider modules:

• jira:jiraDevelopmentTool

• jira:jiraFeatureFlagInfoProvider

• jira:jiraDeploymentInfoProvider

• jira:jiraBuildInfoProvider

• jira:jiraRemoteLinkInfoProvider

• jira:jiraSecurityInfoProvider

• jira:jiraOperationsInfoProvider

• jira:jiraDevOpsComponentProvider

We’ve released a new module, Confluence page banner, which enables apps to add a banner to Confluence pages. This module is generally available.

We are deprecating the following Atlassian Connect-related unscoped npm packages in favor of their @atlassian scoped equivalents.

Starting 23rd of June 2025, these packages will no longer be supported, and we recommend transitioning to the corresponding scoped packages instead.

The affected packages are:

The scoped packages maintain 100% API compatibility with their unscoped versions, ensuring a seamless migration experience. We recommend updating to the scoped versions as soon as possible before the deprecation date.

All of these packages are part of the Atlassian Connect ecosystem and are used for developing Connect apps. The scoped packages provide identical functionality but align with our standardized package naming conventions. This change helps ensure consistency across our npm ecosystem and improves package security.

To update your dependencies, replace the unscoped package names with their scoped equivalents in your package.json files.

If you encounter any issues during migration, please reach out through the Developer Community forums.

We’ve released a new Background Scripts module, which enables apps to run in the background of a Confluence page. See Confluence Background script for more information.

You can use background scripts to replace the atl.footer extension point in Connect.

Forge Remote Data Residency realm migrations is now available in GA. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

We are happy to announce we have added support for macro autoconvert to UI Kit. This allows your app to automatically insert a macro into the editor when a user pastes a recognized URL.

For more details, please see the Macro documentation.

Connect to Forge now supports the migration of the global and permission modules. For more information, see: https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-global-project-permissions/