Changelog

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.

We have now added the ability to use the following as dynamic modules, available under Forge’s Early Early Access Program (EAP):

• Portal header

• Portal request view action

• Portal request detail

To start testing, sign up for the EAP here.

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

We’ve updated how license information is exposed for Forge apps so that the license object is only present for paid, production Marketplace apps, matching our documented behavior.

If you’ve followed the currently documented patterns to check license status, you should not see any change. Our changes may impact apps that rely on custom or undocumented ways of inferring license state for free apps (for example, assuming a license object is present for free installations).

Please refer to our updates docs for more information https://developer.atlassian.com/platform/marketplace/listing-forge-apps/#checking-the-license-status

Forge apps can declare displayConditions in the app manifest for the following JSM portal modules and have them evaluated by the host, consistent with how display conditions work for Jira and Confluence Forge modules today:

• 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

Since the preview release, we’ve also added support for the serviceDesk and customerRequest context variables in the Jira expressions that back display conditions for these modules.

For further details, including available conditions and context variables, see the documentation

Following the EAP release, Feature flags is now generally available for all Forge apps.

Feature flags let you control feature rollouts and manage deployments safely. This GA release introduces front-end (client-side) feature flags in addition to the previously released server-side flags. You can now manage feature rollouts end-to-end across both your backend and UI.

If you participated in the EAP, no migration is required — your existing feature flags will continue to work.

For implementation details and examples, see the Feature flags documentation.

On Dec 26, 2025, we announced a temporary delay to billing for asynchronous Forge app invocations to help you plan and prepare for its upcoming costs. This billing will now commence on Jul 1, 2026.

A Forge app invocation is classified as asynchronous when invoked from the following Forge modules:

• Scheduled triggers

• Async Events API

• Trigger

Usage and cost visibility for asynchronous invocations is now available in the Developer Console. This usage is reported separately from synchronous invocations.

We added a new Installations Permissions page in the developer console that provides a better way to track permissions for each installation used by your app. This page features the following:

• Version & permission details: view each individual installation’s exact permissions and version.

• Scope & egress tracking: this dashboard now features a permission overview for Scopes and Egress, listing each item alongside its current status.

Whenever applicable, the app.license field in the Forge Invocation Token (FIT) received at the Forge Remote during requestRemote calls now contains a real marketplace license (alongside other license fields). Previously, this field could only provide license overrides.

Following the Preview release, the Forge bridge rovo API is now generally available.

The Forge bridge rovo API contains the rovo.open() method, which allows you to open the Rovo chat panel and prompt a new conversation with either a default or specified Rovo agent.

To use this, run npm install @forge/bridge@latest on the command line to install the latest version of @forge/bridge.

For more information, see the documentation.

The Forge platform will be undergoing maintenance in FedRAMP production on March 29, 2026 between 11am - 12am UTC.

There should be a few minutes of downtime within this window. During this time, the following capabilities will not be intermittently available:

• Creating, updating, or deleting apps

• Deploying apps

• Installing, uninstalling, upgrading apps

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

Between Mar 19, 2026 and Apr 10, 2026, all updates to Forge apps with over 50,000 users will be classified as major version updates. You can use the forge version bulk-upgrade command to roll out updates to customer sites during this period.

This temporary change will allow partners to manage the migration of customers in a predictable manner. Downstream services can then absorb the increased traffic without unpredictable spikes.

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

This change will not affect how apps qualify for the Forge revenue share rate. Your latest deployed app version determines revenue share eligibility. Customer roll-out status is not assessed in the eligibility criteria.

A cost dashboard is now available at the developer space level in the developer console, providing a clear, consolidated view of estimated monthly costs for all apps used within that space, calculated from their incurred monthly usage. This dashboard highlights top cost drivers and supports filtering and drill-down, enabling teams to quickly understand where spend is concentrated, investigate anomalies, and make more informed decisions about app usage and optimisation.