You can now migrate a Connect Jira Issue Field module to Forge's Custom Field module. The functionality is now available for Text (text) and Rich Text (rich_text) fields.

See https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields/#text-and-rich-text-fields for more details.

Following Forge modules - jira:customField, jira:customFieldType and jira:issuePanel can now run for unlicensed and anonymous users in Jira and Jira Service Management. This means your apps will work on publicly accessible pages and for users who don't have a full Jira and JSM license.

By default, Forge apps only run for licensed Jira and JSM users. To allow your app to serve unlicensed and anonymous users, add the unlicensedAccess property to your modules in manifest.yml.

Please refer to following guide for more details - https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-users/#introduction.

App developers can now use the connectToForgeMigration manifest module to share their Connect to Forge migration plans and commitment status with Atlassian and their users. This experience is currently limited to developer canary tenants with private apps.

Apps with public Marketplace listings will remain unaffected. However, we encourage you to add this module to your production app, so you can receive the updated behaviour as soon as it goes live.

Please see documentation here.

Going forward, the blanket classification of all updates as major version updates is being replaced with a per-app policy based on each app's migration status.

Apps that have completed the Connect-to-Forge transition: Any app whose latest deployed version contains only Forge modules and scopes -with no remaining Atlassian Connect modules - will be re-enrolled into minor version updates once that version has been released. The proportion of the install base that has upgraded to the latest version is not a factor; what matters is that a bulk-upgrade path existed from the last version that included Connect modules to the current Forge-only version.

54 apps that already meet this criteria have been moved back to minor version updates, and we will be refreshing that list on a weekly cadence.

Apps that have not yet completed the transition: Apps that still include Connect modules in their latest deployed version will not be able to use minor version updates indefinitely. This measure protects platform stability by ensuring that API traffic from these very large apps continues to be managed through controlled rollouts rather than automatic minor-version upgrades.

Backporting changes to older major versions (temporarily restricted)
For now, you can’t publish updates to earlier major versions. This temporary restriction is in place for the same reason large apps were moved to controlled rollouts: to prevent large, high-impact changes from being automatically applied to a significant number of customers and to protect platform stability.

If you need to backport a fix to an older major version, we may be able to make an exception on a case-by-case basis. Please reach out to Atlassian with the app details, the version you need to backport to, and the rationale for the change.

As always, this policy has no effect on how apps qualify for the Forge revenue share rate. Your latest deployed app version determines revenue share eligibility.

For detailed information on how to use forge version bulk-upgrade, see https://developer.atlassian.com/platform/forge/cli-reference/version-bulk-upgrade/.

A back-end change required to safely re-enable minor version updates is in the process of being rolled out. As a result, all updates to Forge apps with over 50,000 users continue to be classified as major version updates.

Please continue to use the forge version bulk-upgrade command to roll out updates to customer sites until further notice. We expect to have this change out the door soon. Please do not rely on minor version updates until the next changelog announcement confirms that it is safe to do so.

Atlassian will discontinue support for the Atlassian Connect Express (@atlassian/atlassian-connect-express) and Atlassian Connect Spring Boot (atlassian-connect-spring-boot) frameworks alongside the end of support for the Atlassian Connect platform.

As of April 30, 2026, Atlassian has ceased development of new features for these frameworks. While we will continue to patch vulnerabilities and assess bug fixes on a case-by-case basis for the time being, this support will end completely when the Connect platform enters its final EOS phase in Q4 2026. When that happens, Atlassian will no longer:

• Investigate or remediate breaking changes caused by product or platform updates.

• Provide official maintenance or security patches for these frameworks

Both frameworks will remain available as open-source projects under the Apache 2.0 license, and their source code will continue to be accessible at:

• Atlassian Connect Express: https://bitbucket.org/atlassian/atlassian-connect-express

• Atlassian Connect Spring Boot: https://bitbucket.org/atlassian/atlassian-connect-spring-boot

Developers who wish to continue using these frameworks can fork and maintain them independently. However, any future maintenance (including addressing breaking changes or security issues that arise after Connect enters EOS) will be the responsibility of the community or individual developers.

For details on the Atlassian Connect EOS timeline and phases, see:
https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps

You can now migrate a Connect Jira Issue Field module to Forge's custom field module. The functionality is now available for Single select and Multi select fields.

See https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields/ for more details.

We've published a new guide - https://developer.atlassian.com//platform/forge/working-around-jql-1000-limit/ - to help Forge app developers handle the custom JQL functions returning more than 1,000 values. The guide covers four practical strategies and code examples, along with trade-off comparisons, and guidance on when to use which approach.

Following our deprecation notice on Sep 29, 2025:

• Customers can no longer install Connect private apps.

• Partners and developers can no longer update existing Jira or Confluence apps using a Connect descriptor on the Atlassian Marketplace.

From now on, private apps can only be installed via Forge installation links. See https://developer.atlassian.com/platform/forge/distribute-your-apps/ for instructions on sharing these links to your customers.

This milestone is in line with our timeline for ending support for the Connect platform.

Forge now supports a preUninstall module, allowing apps to run cleanup logic before uninstallation. Use this to remove stored data, secrets, or other resources when your app is uninstalled. For more details visit https://developer.atlassian.com/platform/forge/events-reference/life-cycle/#life-cycle-events

Forge apps with app.connect.key declared in their manifest can now retrieve the Connect clientKey for an installation via a reserved, read-only app property. See Retrieving the Connect clientKey in Forge for instructions.

We've introduced a new asynchronous bulk API that allows Jira administrators to pin or unpin Forge app issue panels to multiple projects in a single request — processing up to 1,000 projects at once.

For app developers: Integrate this API into your Forge app to give Jira admins a centralized view for managing issue panel visibility across projects. For full API details, see: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-panels/#api-rest-api-3-forge-panel-action-bulk-async-post

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 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.