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.
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.
Following two RFCs related to Dynamic Modules on Forge
https://community.developer.atlassian.com/t/rfc-95-forge-dynamic-modules/92696
https://community.developer.atlassian.com/t/rfc-98-follow-up-forge-dynamic-modules/93532
we are now announcing the start of the dynamic module EAP on the 17th November.
The scope of this EAP will be triggers. More Jira modules will subsequently be released for testing.
As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” (set forth in section 10 of the Atlassian Developer Terms) and are unsupported, subject to change without notice, and are not recommended for use in production environments.
To participate, please sign up for the EAP here.
Note: EAP created dynamic modules will be deleted and not be carried over into Preview phase
To prepare for the migration of Free apps to the new Billing system, we are updating Entitlement ID, Entitlement Number and Start Date of free Cloud app licenses—similar to what’s already in place for Cloud Paid Entitlements.
This update is a foundational step to enable the migration of free Cloud app licenses to the new Billing system, ensuring consistency and future scalability.
Note:
Licenses are not being migrated to the new billing system yet. The migration is scheduled for the first week of November 2025.
Data Field Updates
Identifier Type | Before Change | After Change |
|---|---|---|
| eb000bce00d13c00000eb06d41f86cf2 | 123e4567-e89b-12d3-a456-test |
| eb000bce00d13c00000eb06d41f86cf2 | E-XXX-XXX-XXX-XXX |
| Dec 5, 2023 | Nov 7, 2025 (placeholder, the day of migration) |
| Null | Null |
The change is estimated for 250k+ free Cloud app licenses spread across Marketplace Partners. Entitlement ID values and Entitlement numbers will be updated for the the following APIs that provide license details:
Partners can fetch the updated appEntitlementId and appEntitlementNumber using the lastUpdated field.
Do a one-time export of all free Cloud app licenses (licenseType == Free) before the migration (by Oct 31, 2025)
Include: appEntitlementId, appEntitlementNumber, maintenanceStartDate, addonKey, cloudID, parentProductName.
After the update, map the new appEntitlementId to the UUID using unique identifiers (addonKey, cloudID, parentProductName) to obtain the new appEntitlementId and new maintenanceStartDate.
If you have questions or need more details, please contact us through ECO-HELP tickets.
Following this migration:
Any updates to product compatibility in a public app version will require you to release a new version of your app.
All the inactive free licenses will be removed from reporting.
The Forge Model Context Protocol (MCP) Server is now in preview. This new remote service enables Forge app developers to use coding agents with up-to-date Atlassian Forge and Cloud documentation, including markdown-based guides, module catalogs, and manifest references. The Forge MCP Server also offers a search feature for Forge reference documentation and implementation patterns. These features are designed to streamline Forge app development in AI-powered workflows. We invite you to try the Forge MCP Server (preview) and share your feedback to help us improve.
Try the Forge MCP Server (preview) and share your feedback to help us improve.
For more information, see Forge MCP Server documentation.
We’re announcing the deprecation of the V2 Reviews APIs on the Atlassian Marketplace.
What’s changing
The V2 Reviews APIs are now deprecated.
A six-month deprecation window begins immediately, and this API will be removed on April 23, 2026.
Review the latest V3 Reviews APIs for more details.
What you need to do
Partners and developers should migrate to the V3 Reviews APIs to ensure continued functionality and support.
Rate this page: