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.
We're updating the cursor behavior in the Storage Remote GraphQL API for both Key-Value Store (KVS) and Custom Entity stores. Currently, KVS returns individual cursors for every edge, while Custom Entity edge cursors always point to the last element of the current page. To reduce confusion and align with the new REST API, both stores will now return a single cursor at the end of each page.
This change will take effect after March 20, 2026.
More details:
After this change, the response will still include a cursor for every edge, but each cursor will point to the end of the page for both KVS and Custom Entity stores.
If your integration relies on the previous cursor behavior, update your code to handle the new logic before March 20, 2026.
All future updates to KVS and Custom Entity Store will only be available through the REST API. If you're planning to integrate Forge-hosted storage into a remote service, use the REST API.
For more information, see:
We've updated our documentation to clarify the existing rate limits for network requests and web trigger operations in Forge. These limits have been in place to protect the reliability and stability of our platform, but are now described in more detail to help developers understand how they apply.
No new limits have been introduced, and there are no changes to enforcement.
The documentation now clearly outlines the specific rate limits for network requests and web triggers, including how limits are calculated and what happens if they're exceeded.
If your app is already operating within the established limits, no action is required.
For details on the documented limits, see the https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/#network-requests-and-web-triggers.
New features:
The following are the new commands:
🆕 acli jira workitem link create command to create links between work items.
🆕 acli jira workitem link delete command to delete links between work items.
🆕 acli jira workitem link type command to delete link types between work items.
🆕 acli jira workitem link list command to get the available work item lists.
🆕 acli jira workitem comment list command to list comments for a work item.
🆕 acli jira workitem comment visibility command to get visibility options for work item comments.
🆕 acli jira workitem attachment list command to list all the attachments of a work item.
Bug fixes and enhancements:
Various bug fixes and improvements have been made to enhance overall functionality and performance.
While version 3 of the Marketplace App Migration APIs is still under development, we’re releasing the documentation for these Marketplace App Migration APIs early to help you prepare for the upcoming changes. This release includes a preview of the API documentation schema and examples of API requests and responses.
To ensure smooth transition with the upcoming changes, we recommend to review the API documentation to understand and prepare for the upcoming changes.
Here are some helpful suggestions for you to consider:
Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.
Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.
Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.
Following our prior deprecation notice, you can no longer publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace.
From now on, all Atlassian Marketplace apps should be built using Atlassian’s Forge platform.
Learn more about the announcement of our timelines for the end of support for Connect. Existing apps built with Connect should explore https://developer.atlassian.com/platform/adopting-forge-from-connect/.
What’s changing?
To help initiate Atlassian’s migration of Data Center licenses to the new Billing system, we are introducing Entitlement Numbers to Data Center (DC) licenses—similar to Cloud Entitlements.
Note: Licenses are not being migrated to the new billing system yet.
Data Field Updates
Identifier Type | Before Change | After Change |
|---|---|---|
| SEN-1234567 | SEN-1234567 |
| Null | 123e4567-e89b-12d3-a456-test |
| Null | ENT-123-ABC-123-ABC |
The change is estimated for 200K+ Data Center licenses spread across Marketplace Partners. Entitlement ID values and Entitlement numbers will be updated for the the following APIs that provide Data Center license details:
Partners can fetch the Updated appEntitlementId & appEntitlementNumber using the lastUpdated field.
Why are we doing this?
The change will help lay the foundation for future migration of Data Center licenses to the new Billing system.
Further communications on migration dates/ cohorts will be provided in QRG and Change-logs.
If you have questions or need more details, please contact us through ECO-HELP tickets.
:info: Please note: We initially planned to go live on 19 September 2025; however, due to a deployment issue, we now aim for the coming week. We will provide an update via the Changelog before the changes go live.
We're changing how Forge app installations are managed for Bitbucket workspaces. To align with our platform strategy and meet enterprise and regulatory requirements, Bitbucket workspaces must be linked to an Atlassian organization to continue using Forge apps. This change will help us support new features like cross-product apps and data residency.
This change will take effect sometime after March 16, 2026. More details will be available closer to that date.
After the deprecation period, Forge will no longer support apps for Bitbucket workspaces that aren't linked to an Atlassian organization.
Workspaces that aren't linked will have their existing Forge app installations deleted and won't be able to install new Forge apps.
Onboarding happens automatically once a workspace is linked to their company’s Atlassian organization.
To avoid disruption:
Customers need to link their Bitbucket workspace to an organization as soon as possible.
If there are any issues linking workspaces, contact Bitbucket support.
If customers can't link their workspace, but want to keep app data after the deprecation period, contact Ecosystem support.
For step-by-step instructions and more details about this change, check out our community post: Connect your Bitbucket workspace to an Atlassian organization.
Forge platform will be undergoing maintenance:
in FedRAMP production on September 21, 2025 between 5-6am UTC
in commercial production on September 28, 2025 between 5-6am UTC
During this interval, below capabilities will not be available intermittently:
Create/update/delete apps
Deploy apps
Install/uninstall/upgrade apps
App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.
On or after December 10th, 2025, we are deprecating the endpoints:
/scim/v2/users
/scim/v2/groups
Please use the REST API to retrieve information on Trello Users or Members, more specifically:
Trusted apps authentication has been removed. For details, see Removal of Trusted apps.
A supported migration path is available via OAuth 1 with impersonation.
Details
OAuth 1 with impersonation allows plugins to generate signed HTTP requests back to the same Data Center instance while impersonating a specific user.
Relevant ticket: CONFSERVER-99078 – Java API for authenticated HTTP requests to current Confluence instance.
A demo plugin illustrates how to implement OAuth 1 with impersonation for both Jira and Confluence: https://bitbucket.org/atlassian/dc-platform/src/4407b6ea004529ba93a69315d99765657ce7829b/demos/oauth1-impersonation-plugin-example/?at=release%2F8.0.x.
OAuth 1 with impersonation is already part of the existing OAuth 1 plugin.
Product Changes
Jira 11.0.1 (released) and Confluence 10.0.4 (scheduled for release) now automatically create a host consumer provider on the product side, enabling plugins to connect back to the same Data Center instance.
The allow-popups attribute of the sandbox directive (content security policy) is now supported in Forge Custom UI and UI Kit apps when using * as your client egress configuration. This enables external content (such as those from 3rd party integrations) to open properly in new tabs instead of being blocked by browser security restrictions.
With this enhancement, external content will open in a new browser tab while keeping your Forge app running.
For more information, see the valid domain formats documentation.
Forge Realtime is now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
Realtime allows Forge apps to subscribe and publish events to users in different browsing contexts, including the ability to publish events from Forge resolvers to the client.
This feature is only available in Jira, with support for other products to be available soon.
For more information, see the Realtime documentation.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.1 and Jira Service Management 11.1. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.1.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.1.0-m0012.
This EAP release isn't for production or demonstration use.
A Confluence 10.1 EAP milestone is available now for testing. To find out what’s changed, check out Preparing for Confluence 10.1.
Got feedback or want to discuss the latest EAP? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
We’re excited to announce Bitbucket Data Center 10.0 – the newest platform release since July 2024.
Based on Bitbucket 9.0, the latest platform release, Bitbucket 10.0 includes useful features for:
full-color accessibility mode
multiline comments and suggestions
new login experience with two-step verification
default reviewer groups for pull requests
secure app installations with app signing
security monitoring and alerts
enhanced security for database-stored secrets
Learn more about the new features in the release notes
To update your Bitbucket license:
Go to Administration > Licensing.
Select Edit license and enter your Data Center license key.
Select Save.
Rate this page: