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.
From Apr 30, 2026, the nodejs20.x runtime will be deprecated. This is in line with the Node.js version 20.x end-of-life, scheduled for Apr 30, 2026.
You must update your apps to use the newer nodejs22.x runtime before this date. Otherwise, you will not be able to deploy changes to your app.
We’re announcing the deprecation of the V2 Privacy and Security APIs on Atlassian Marketplace.
What’s changing
The V2 Privacy and Security APIs are now deprecated.
A six-month deprecation window begins immediately, and these APIs will be removed after April 30, 2026.
Refer to the updated documentation for V3 Privacy and Security APIs to plan your transition.
What you need to do
Partners and developers should migrate to the V3 Privacy and Security APIs to ensure continued functionality and support.
Following its review release, we are excited to announce that the V3 Privacy and Security APIs are now generally available on the Atlassian Marketplace. This means these APIs are now fully operational and can be used in production environments.
For more information, see V3 Privacy and Security API documentation.
From Nov 1, 2025, Atlassian will migrate all Forge apps to a new app lifecycle platform. This migration introduces changes to how the platform handles apps with inactive licenses:
Unified uninstall flow:
Unsubscribing and uninstalling an app will be combined into a single ‘uninstall’ action.
When an admin selects ‘uninstall’, the app will remain active until the end of the current subscription or trial period, plus an additional 60 days, before it is permanently deleted. No further user action is required during this period.
Expedited uninstall:
Admins can choose to expedite the uninstall process. This will immediately uninstall the app and forfeit any remaining subscription period.
Legacy “free” licensing state:
Apps that have already passed the end of their subscription or trial period will temporarily transition to a legacy “free” licensing state. These inactive installations will not thus be affected by the new uninstall flow until an admin initiates an uninstall action.
Partners are encouraged to request that customers either re-subscribe or uninstall these apps.
Read more in the community post and our support doc.
Going forward, when an license lapses, apps will move through an suspend/delete cycle, providing time for customers to renew a license to maintain use.
You can check your license state as described in our documentation. Legacy “free” installations will show as license.active: false.
When the app data is stored within Atlassian, it can be recovered for 30 days. After this period, the data will be deleted.
New features:
The following are the new commands:
🆕 acli jira board list-sprints command to get all sprints.
🆕 acli jira board search command to search through all the boards.
🆕 acli jira field create command to create a custom field in Jira.
🆕 acli jira field delete command to move a custom field to trash.
🆕 acli jira field cancel-delete command to restore the field from the trash.
🆕 acli jira filter list command to list filter that are either my or favourite.
🆕 acli jira filter add-favourite command to add a filter as favourite.
🆕 acli jira sprint list-workitems command to list work items in a sprint.
🆕 acli jira workitem attachment delete command to delete an attachment from a workitem.
🆕 acli jira workitem comment delete command to delete a comment for a given workitem.
🆕 acli jira workitem comment update command to update a comment on a work item.
🆕 acli jira workitem create-bulk command to bulk create Jira issues.
🆕 acli jira workitem watcher remove command to remove a watcher from workitem.
A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-117-forge-llms/96506
As part of previously announced changes to improve diff performance, Bitbucket Cloud’s compare two commits and compare two diff stats REST endpoints will begin returning a topic diff (three-dot diff) by default, instead of the current default, preview-merge diff.
This change will be effective November 17, 2025.
Consumers can specify the merge=true parameter to explicitly request a preview-merge diff. This parameter is already supported but will be removed in the future. We will post a separate changelog entry when we have further details about the timeline for its removal.
To maintain trust in the Runs on Atlassian (RoA) program, apps that use Atlassian API tokens (personal access tokens) to interact with first-party apps are no longer eligible for the RoA badge. Such apps will lose their RoA eligibility on Nov 3, 2025.
Apps must rely solely on oauth scopes and leverage the built-in api.asUser or api.asApp functions to call first-party app APIs.
On Apr 1, 2025, we stopped granting waivers for apps to use Atlassian API tokens. You must phase out API token use by Dec 31, 2025.
You can now provide dynamic descriptions for the configuration of Forge workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.
Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.
You can now enable your Forge workflow conditions, validators and post functions in team-managed workflows. Use the projectTypes property to configure whether your rule should be enabled for company-managed projects, team-managed projects, or both.
You can now provide dynamic descriptions for the configuration of Connect workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.
Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.
AppDataListResponse in the Forge migration API has been updated to match the actual response.
Previously, the definition didn't match the API response, which could cause cast errors or undefined object errors when accessing response fields. This fix ensures the response structure is consistent with the API documentation, so the API can be effectively used to migrate apps from Server or Data Center to Cloud.
If you were using the previous definition, you may see a compile error after updating. To resolve this, change any usage of response.result to response when calling this API.
The following UI Kit Editor components are now available through Forge’s Early Access Program (EAP). To join, please complete this sign-up form.
These components are available in Confluence and Jira modules.
A new RFC is ready for review at : https://community.developer.atlassian.com/t/rfc-116-new-link-egress-type-for-forge-apps/96445
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.2 and Jira Service Management 11.2. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.2.
In this EAP, we’ve marked the Instance optimizer safeguards as breaking change. More about safeguards breaking changes
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.2.0-m0041.
This EAP release isn't for production or demonstration use.
Rate this page: