This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.
To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.
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:
Usage and cost visibility for asynchronous invocations is now available in the Developer Console. This usage is reported separately from synchronous invocations.
We’ve added experimental CSM REST APIs for deleting individual customers and organizations:
Refer to API quick start for information on how to get started with the CSM REST API.
📢 Rollout: progressive rollout by app. ongoing
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.
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.
This capability is only being provided temporarily to facilitate migration away from the Connect installed lifecycle webhook, which previously was the only way to obtain the clientKey. It will only be supported for as long as Connect is supported. For more information about the timeline for Connect end-of-support, refer to this blog.
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.
We are releasing a new version of ACLI that introduces additional OAuth scopes required for upcoming features and platform security improvements.
Because of these new scopes, site admins must re‑authorize ACLI for each connected site. Until re‑authorization is completed, users may see the following error when trying to use ACLI with their site:
Your site admin must authorize this app for the site "<PLACEHOLDER_YOUR_SITE>" before the app can access your account.
Action required
Site admins need to re‑approve the ACLI app for all affected sites, as mentioned in the details section below.
After re‑authorization, ACLI will work as expected with the updated permission set.
No other behavior changes are expected in this release.
The process is as follows :
Since this is not a marketplace app, the admin (site-admin) needs to manually upgrade to the latest version on their machine: https://developer.atlassian.com/cloud/acli/guides/update-install-guide/
The admin needs to go through the OAuth flow by running: acli jira auth login , selecting the "Web" option that opens up the OAuth consent screen, and then selecting the site they need to re-approve.
As we transition to the new Marketplace v3 APIs, the ECOHELP app approval process now comes with new statuses for better visibility:
approved - Congratulations, your app has been approved and sent for publishing in the backend.
Published - Your approved app is now available and visible on the Marketplace.
:info: The rejection status awaiting resubmission is applicable for both v2 and v3 APIs and the legacy approval status Closed may still be in use when v2 APIs are triggered.
We introduced an optional legacyListingDetails field to the Marketplace v3 API endpoint:
PUT /rest/3/product-listing/{productId}
Although optional, we strongly recommend using this field in update requests to prevent legacyListingDetails data from being overwritten as null.
The legacyListingDetails field, familiar from v2 APIs, now appears in v3 response payloads and as an optional property in PUT requests.
When present, it provides legacy listing details for the app, including description, wikiLink, sourceLink, and buildsLink. All fields are optional and use proper URI formatting.
Action required
We strongly recommend using the legacyListingDetails field when making PUT requests to avoid this field being overridden as null in the response.
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.
Along with ALL_OF, NONE_OF, SOME_OF types of field check in section conditions, we now support BETWEEN, CONTAINS, DOES_NOT_CONTAIN, EQUAL_TO, DOES_NOT_EQUAL, GREATER_THAN, GREATER_THAN_OR_EQUAL_TO, LESS_THAN, LESS_THAN_OR_EQUAL_TO, EMPTY and NOT_EMPTY.
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.
As discussed in RFC-124: Evolving the Marketplace Trust Program, we will retire the Cloud Security Participant badge on Mar 31, 2026. We will continue to highlight partners’ investment in the Bug Bounty program on the app listing for both cloud and Data Center apps.
Starting Mar 31, 2026, the Cloud Security Participant badge will be removed from:
App tiles shown in search results and collection pages
The top of the app listing page (under Trust Signals), as shown below
Trust signal filters, as shown below
We’ve introduced an optional legacyListingDetails field to the following Marketplace v3 API endpoints:
GET /rest/3/product-listing/{productId}
GET /rest/3/product-listing/developer-space/{developerId}
What’s changing
The new legacyListingDetails field, known from v2 API where it was called AddonLegacyProperties, is now available in GET v3 response payloads.
Note that legacyListingDetails has a different structure than AddonLegacyProperties. When present, it provides details of the legacy listing for the app, including description, wikiLink, sourceLink, and buildsLink.
All fields are optional and use proper URI formatting.
Action required
No action is required unless you want to start consuming the legacyListingDetails field in your integration.
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.
Rate this page: