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.
In the previous pricing announcement, the SQL Data stored metric used an average model with billing unit in GB. We are shifting to a sum/counter model. To prevent financial implications from this change, we are adjusting the billing unit, monthly quota, and pricing.
Starting today, the developer console and cost estimator will reflect this change. SQL data stored usage in the developer console will now be displayed in GB-hours.
Aspect | Earlier announced model | New model |
|---|---|---|
Billing Unit | GB | GB-hour |
Monthly Quota | 1 GB per month | 730 GB-hours per month |
Pricing | $0.561 per GB | $0.00076850 per GB-hour |
Usage Tracking | Hourly snapshot data averaged over the month | Sum of hourly reported usage |
With immediate effect, the Developer Console will display near real-time usage data for all chargeable capabilities. In rare cases, a delay of a few hours may occur before the latest usage appears.
You don’t need to take any action. This change does not affect your free usage threshold or increase your costs.
For more information, see the Forge platform pricing.
The following Object Store UI components are now available for through Forge’s Early Access Program (EAP):
UI Kit components:
File picker: allows the user to select files stored locally.
File card: displays information about a file (including name, type, and size); this can be used to managed selected files and displaying upload progress.
Frontend components for integrating with the Forge Object Store via backend resolver:
useObjectStore hook method (for apps that use UI Kit)
objectStore bridge API (for apps that use Custom UI)
To start testing these capabilities, please go here.
These UI components were built to simplify seamless integration with the Forge Object Store, which is also available through EAP. To start testing this backend, you’ll also need to sign up for its EAP.
The Batch operations capability is now generally available, allowing you to execute multiple KVS and Custom Entities requests simultaneously. These batched requests are executed in parallel, and each requests will be completed on a “best effort” basis (unlike Transactions, where all requests are completed in an “all or nothing” basis).
This capability was originally launched in EAP as Bulk Set; on Sep 3, 2025 we closed this EAP in preparation for general availability.
Batch operations is included in version 1.2.0 of the @forge/kvs package.
Bitbucket Data Center 8.19.25, 9.4.13, and 10.0.2 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-118-cloud-to-cloud-identifier-mapping/96871
Following its EAP release, Forge Realtime is now available in preview for Jira and Confluence.
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. During Preview, Realtime can be used in production environments for your app.
Since the EAP release, we’ve implemented the following changes:
To use global channels, you must now include the Realtime read:app-global-channel:realtime scope in your manifest. Users will then need to upgrade their installation of your app.
The contextOverrides option now accepts Confluence context properties.
Event payloads can now be JSON-serializable objects without needing to be stringified first. String payloads are still supported.
Run the following commands on the command line in your app directory to install the latest version of these packages and receive these changes:
npm install @forge/bridge@latest
npm install @forge/realtime@latest
For more information, see the Realtime documentation.
Date: 2025-11-10
We recently identified an issue affecting approximately 30,000 Cloud license records on the Free starter tier. Following the migration from the old billing system to the new billing system, these licenses (entitlements), distributed across multiple marketplace partners, were incorrectly marked as churned.
We have now corrected these records in the licenses API, ensuring that their status accurately reflects the following:
licenseType: Free
In addition, the corresponding churn data, shared via cloud churn API has been updated to reflect these changes.
This fix is part of ongoing improvements to support the migration of Cloud licenses to the new Billing system. The update ensures that license status data is accurate.
Action for Partners:
Partners can retrieve the updated data using the lastUpdated field in the Licenses API.
Following its review release , we are excited to announce that the Marketplace V3 App listing and App version listing APIs are now generally available. This means these APIs are now fully operational and can be used in production environments.
For more information, see V3 App listing APIs and V3 App version listing APIs
Starting from CCMA 3.13.1 and JCMA 1.12.47 and `atlassian-app-cloud-migration-listener` version 1.8.7, you can use the Object Store data plane to migrate data into Forge Object Store from Server/DC.
The Confluence full page module is now available in Preview. After a successful Early Access Program (EAP), we’re making the module more broadly available for developers to build fully customised app experiences within Confluence.
The EAP URL is now deprecated and will no longer work. Please update your bookmarks and use the new Preview URL format.
More details:
Old EAP URL (deprecated):<https://<tenant-name>/wiki/full-page/<app-id>/<environment-id>>
New Preview URL (Forge Apps UI Service):<https://<tenant-name>/forge-apps/a/<app-id>/e/<environment-id>/r/<route-prefix>/<app-route>>
For more information, see the Confluence full page (Preview)
We’re announcing the deprecation of the V2 Applications APIs on Atlassian Marketplace.
What’s changing
The Applications APIs are now deprecated.
A six-month deprecation window begins immediately, and these APIs will be removed after May 6, 2026.
Refer to the updated documentation for V3 Parent software APIs to plan your transition.
What you need to do
Partners and developers should migrate to the V3 Parent software APIs to ensure continued functionality and support.
We’re happy to present the release of Jira Software and Jira Service Management 11.2. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.2 release notes and Jira Service Management 11.2 release notes.
Download Jira Software 11.2 and Jira Service Management 11.2.
The ability to build Forge apps that are compatible with multiple Atlassian apps is now available in Preview. This feature allows you to declare compatibility in your app’s manifest and enables your app to be installed and used across Jira, Confluence, and Compass.
For more information, see App compatibility.
The following flows are available for testing in this Preview:
Create, deploy, and install an app via the CLI
Distribute the app via a direct distribution link
View and connect/disconnect compatible Atlassian apps in Connected Apps
Add the app to Marketplace
Important considerations:
Customer release (GA) is planned for the end of January 2025.
Until GA: We recommend keeping Marketplace apps private, as customer-facing changes are not yet available (admins currently only see the required app in the consent screen when installing).
For guidance on migrating existing apps, see our migration guidelines.
We’ve added new Confluence Forge events for relations:
avi:confluence:created:relation
avi:confluence:deleted:relation
You can use these events to invoke your Forge app function when a relationship is created or deleted in Confluence. For more details, see the Confluence events reference documentation.
Following our prior deprecation notice, the following internal API endpoints will now result in a 404 Not Found response.
/wiki/rest/masterdetail/1.0/detailssummary/lines
/download/thumbnails/{id}/{id}
/download/resources/{id}/icons/{id}
/download/resources/{id}/{id}
/download/resources/{id}/images/{id}
Learn more in our prior deprecation notice.
Rate this page: