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 are re-enabling automatic Connect to Forge migrations, following the temporary pause which started on Sep 23, 2025

Apps which were impacted by or published to the marketplace following this pause will now see Connect installations progressively move to Forge as long as they meet the minor update criteria. The pace of the migration will be dynamically adjusted to ensure high throughput and reliability of the pipeline as we clear these pending updates.

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.

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.

Forge platform will be undergoing maintenance in commercial production on October 12, 2025 for approximately 1 minute between 3-4am 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.

Starting Mar 31, 2026, the ability to update existing Jira or Confluence apps using a Connect descriptor on the Atlassian Marketplace will be deprecated. This change aligns with our strategic shift to the Forge platform.

Additionally, this means the following:

1. Atlassian Marketplace will no longer poll for Connect descriptor updates. However, apps using Connect modules that have adopted the Forge manifest can still receive updates.

2. Installing new Connect private apps via Connected Apps will no longer be available and private app development should move to Forge.

What this means for partners:

1. Partners should plan to update Connect apps on the Atlassian Marketplace by Mar 30, 2026 at the latest.

2. All new app development should be conducted on Forge.

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