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.
The app.version property in FIT contains a string used by some internal Atlassian services. As such, it does not accurately represent the actual app version. To refer to the correct Forge app version, use the new app.appVersion property instead.
The app.version property will be removed on Sep 25, 2025.
In the latest version of @forge/react, we're adding a new disableSubmitOnBlur property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value on blur events.
For more information on this component, see the component documentation.
To update your UI kit app to the latest version, run the following command in your project directory:
npm install --save @forge/react@latest
We’ve added V2 API endpoints to retrieve children and descendants for pages, databases, smart links, whiteboards and folders.
To enable these new V2 APIs, you’ll need to use the new Oauth 2.0 scope read:hierarchical-content:confluence.
These new APIs correspond to the following V1 APIs, which have been marked as deprecated (and will be retired on Apr 30, 2025):
Here are the new V2 endpoints:
/pages/{id}/direct-children/pages/{id}/descendants/databases/{id}/direct-children/databases/{id}/descendants/embeds/{id}/direct-children/embeds/{id}/descendants
/whiteboards/{id}/direct-children/whiteboards/{id}/descendants/folders/{id}/direct-children/folders/{id}/descendants
From Apr 30, 2025, uploading visual marketing assets through app artifacts (.jar, .obr, or .jwb) will no longer be supported. Instead, partners now have the option to use either the UI or the APIs to upload their branding assets, both of which are already available.
You can continue to upload your software using the existing option or the API. However, to upload marketing assets, you must use the publish experience or the API and upload the assets during that process, rather than using the app artifact upload option.
This change is part of the broader Marketplace Technical Foundations initiative.
For any comments or questions, please submit a support request.
After the deprecation period on Apr 30, 2025, you will not be able to use the following options to upload your marketing assets:
App logo: Navigate to the About app section, and select Upload logo.
Page design assets: Navigate to the Page Design section, select the desired page design type, and click the Add Another Image button to upload your assets.
We have identified an issue with the display of Solution partner type & solution partner billing contact emails in our reports.
Previously, partner type field, partnerDetails.partnerType displayed ‘Unknown’ for 26,000 transactions in transactions API across Marketplace partners.
Additionally, in partner detail, the billing contact email and name field -partnerDetails.billingContact for solution partners incorrectly displayed Atlassian email addresses for some licenses in licenses API across Marketplace partners.
These issues have now been corrected as of Mar 21, 2025 . Marketplace partners can access accurate Partner types and billing contact emails using the lastUpdated field in the in the Get licenses and Get transactions API respectively.
The Forge SQL service’s cluster will be upgraded during a routine maintenance window on Mar 24, 2025 from 21:00 - 21:30 UTC. During this time, control plane operations (such as fresh installations or upgrade of an app that uses SQL capability) may fail intermittently. Data plane operations such as SQL queries will continue to work as normal. Other Forge storage capabilities will not be impacted during this maintenance window.
The Jira workflow validator function has been enhanced to provide additional details about fields that have been modified during a work item transition.
To see list of all supported field types, please refer to the documentation: Jira Workflow Validator.
Connect to Forge now supports the migration of the global and permission modules. For more information, see: https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-global-project-permissions/
We are extending the deprecation period for all endpoints noted in Deprecation of v1 Confluence Cloud API endpoints and Deprecation of v1 Confluence Cloud API Endpoints to April 30, 2025.
We have identified an issue with the display of license status and licenseType for Sandbox licenses migrated to the new billing system. Post-migration, these licenses incorrectly displayed status as Cancelled and licenseType as Commercial on the licenses API and Marketplace reporting user interface.
This issue is now fixed and the migrated sandbox licenses correctly display active status and FREE licenseType for ~ 10k license lines across all Marketplace partners. The updated records for Sandbox licenses can be identified using the following fields and values in the Get licenses API:
installedOnSandbox - Is Sandbox
status - Active
licenseType - FREE
Marketplace Partners can access updated license records using the lastUpdated field.
After the beta phase of Atlassian’s new navigation, we’re thrilled to announce its General Availability (GA) for Jira, Jira Service Management, Jira Product Discovery, Confluence, and Atlassian Home. In this article, you’ll find key details about what’s changing with the new navigation, Jira and Jira Service Management apps, as well as when those changes will go live.
Bitbucket Data Center 9.6 is available for upgrade! This release introduces new features, such as two-step verification support for websudo, secure app installations with app signing, full-color accessibility mode, repository search index insights, and more.
The Export App logs API now features two new query parameters:
message: lets you filter by the contents of a log’s message.
installationContext: lets you filter by site ID.
A Confluence 9.4 beta version is available now for testing. To find out what’s changed, check out Confluence 9.4 beta release notes.
Got feedback or want to discuss this beta? 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.
Starting Sep 17, 2025, the ability to publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace will be deprecated. This change is part of our strategic shift to the Forge platform that enables developers to leverage enhanced capabilities such as Forge Storage.
Partners should plan to list any Connect apps currently under development on the Atlassian Marketplace by Sep 16, 2025, and should undertake all new app development on Forge.
Documentation on adopting Forge from Connect, capabilities equivalences between Forge and Connect, and other details about the transition from Connect to Forge for Jira and Confluence apps are available on the Adopting Forge from Connect content site.
Rate this page: