This page includes changelog entries and updates related to adopting Forge from Connect. Use this page to keep track of what Connect equivalent functionality is being shipped in Forge, and what resources are being added to help you move from Connect to Forge.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
We’ve introduced a platform-level URL persistence and redirect feature for apps migrating from Connect to Forge. Jira and Confluence will now accept legacy Connect URLs (including full path, query parameters, and fragments) and transparently redirect them to the corresponding Forge app module. For more information on how it works, please see the documentation here.
You can now nominate genuine migration blockers or major customer‑impact risks via the “Request review” flow on FRGE issues.
This flow will allow us to triage and assess requests to address remaining blockers to Forge migration before Connect end of support in December 2026. We’ll review requests over 3 monthly cycles, then freeze decisions.
Please review for existing tickets before creating new FRGE tickets. You may also review the announcement.
We’ll publish the outcomes of these decisions on the following pages:
Approved / available capabilities:
https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-forge-equivalences/connect-forge-capabilities-available/
Not‑available capabilities (including rejected requests):
https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-forge-equivalences/connect-forge-capabilities-notavailable/
We are introducing baseline security requirements for Atlassian Government Cloud (AGC) apps, which will take effect on Mar 31, 2026. If you have any questions regarding these new standards, please contact us here: https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/109/create/579
We’re also publishing our annual update to the general Cloud App Security Requirements for 2026, which includes new provisions for AI security, data protection, and supply chain security. See More details for highlights on this update.
Key additions to the general Cloud App Security Requirements include:
AI Security: New requirements for apps using Forge Rovo actions and agents, including validating action inputs as untrusted, implementing permission checks for admin-level actions, and accurately configuring actionVerb values.
Data Protection:
External OAuth2 clients must use Forge's OAuth2 Providers and be configured as confidential clients where supported.
Application logs must strictly exclude PII, credentials, and sensitive data.
Apps must ensure strict tenant isolation during runtime.
Apps must not execute arbitrary code by spawning child processes (e.g., using Node.js child_process).
Application Security:
Apps using Forge SQL must use parameterized queries to mitigate SQL injection risks.
Updated guidance on Content Security Policy (CSP) regarding unsafe-inline and unsafe-eval directives.
Runtime Security:
Apps must not use EOL (end-of-life) Node.js runtimes.
We’re introducing display condition support to the following Jira Service Management (JSM) Forge portal modules as a preview release:
Portal footer
Portal header
Portal profile panel
Portal request create property panel
Portal request detail
Portal request detail panel
Portal request view action
Portal subheader
Portal user menu action
For these JSM modules, Forge apps can now declare displayConditions in the app manifest and have them evaluated by the host, consistent with how display conditions work for Jira and Confluence Forge modules today.
For further details, see the documentation here.
You can now migrate a Connect Jira Issue Field module to Forge's custom field module. The functionality is now available for String, Number and Read-only fields.
See https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields/ for more details.
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:
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.
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:
Partners should plan to update Connect apps on the Atlassian Marketplace by Mar 30, 2026 at the latest.
All new app development should be conducted on Forge.
See the Adopting Forge from Connect documentation to know more about how to migrate to 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.
More details:
After this change, the response will still include a cursor for every edge, but each cursor will point to the end of the page for both KVS and Custom Entity stores.
If your integration relies on the previous cursor behavior, update your code to handle the new logic before March 20, 2026.
All future updates to KVS and Custom Entity Store will only be available through the REST API. If you're planning to integrate Forge-hosted storage into a remote service, use the REST API.
For more information, see:
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.
Learn more about the announcement of our timelines for the end of support for Connect. Existing apps built with Connect should explore https://developer.atlassian.com/platform/adopting-forge-from-connect/.
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.
Rate this page: