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 announcing the deprecation of the V2 App migration APIs on Atlassian Marketplace.
What’s changing • The V2 App Migrations APIs are now deprecated. • A six-month deprecation window begins immediately, and these APIs will be removed after May 18, 2026 . • Refer to the updated documentation for V3 App Migration APIs to plan your transition.
What you need to do Partners and developers should migrate to the V3 App migration APIs to ensure continued functionality and support.
Multi-instance pricing is now live, enabling Cloud Enterprise customers to be charged based on the number of unique users of an app across multiple instances, regardless of the number of product instances.
Multi-instance pricing: Partners must offer multi-instance pricing for paid cloud apps alongside single-instance pricing, with flexibility to set different prices.
Existing apps: Multi-instance pricing will be enabled by default, initially matching single-instance pricing.
Pricing: The pricing console will default multi-instance pricing to 1x of single-instance pricing, but partners can adjust this multiplier or edit fields as needed.
Partners can set multi-instance pricing as a price multiplier (≥1x of single-instance pricing) and edit pricing across different user tiers.
Partners, if you have not already set your multi-instance pricing, then we recommend that you update it as soon as possible.
Learn more here or via the developer documentation
Following its review release , we are excited to announce that the Marketplace V3 App migration 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 migration APIs .
Following its review release , we are excited to announce that the Marketplace V3 App software 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 software APIs and V3 Asset APIs.
The sidebar will now span the full height of your Atlassian app, making it easier to find and interact with. Starting late November 2025, this update will roll out to all customers who haven’t customized the look and feel of their sites. This change won’t affect the width and height of your Forge and Connect apps.
Along with this, we’re introducing a few improvements to sidebar interactions:
Double-click to collapse: When expanded, double-click the button to quickly collapse the sidebar.
Global shortcut: Use Ctrl + [ to expand or collapse the sidebar at any time.
Helpful tooltips: Tooltips will appear to guide you through the interaction.
For sites with customized look and feel, the full-height sidebar can disrupt intentional design choices, such as:
Custom logos and titles
Favicons
Navigation colors
Dark and light mode settings
Because of this, the sites with customized look and feel won’t receive the update just yet.
For the sites without customized look and feel, we’re opening up the opportunity on Nov 21, 2025 to let you use this feature early and test it with your apps. If you’re interested, please sign up here with your site details.
As announced previously, the ability to use triggers as a dynamic module is now available under Forge’s Early Access Program (EAP).
To start testing, sign up for the EAP here.
As part of our new design language, the refreshed colors and components in the Atlassian Design System (that first launched in products at Team '25) are now officially in GA. Also included is a further tweak to accent token colors in hover/pressed states to improve accessibility.
What you need to do if you are using Forge Custom UI or Atlassian Connect:
Bump @atlaskit/tokens + relevant component packages to the latest version to align your app's look and feel with Atlassian apps.
What you need to do if you are using Forge UI Kit or Forge UI Kit 2:
Nothing! You should have the newest components by default.
Visual changes to Atlassian components and tokens:
New base color tokens: We've introduced new color stops across our base color ramps, namely 250 and 850, to support better hover/pressed state contrast and improve WCAG AA accessibility.
We’re happy to present the first Early Access Program (EAP) build of Jira Software 11.3 and Jira Service Management 11.3. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.3.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.3.0-m0002.
This EAP release isn't for production or demonstration use.
The GET methods of the Key-Value Store and Custom Entity Store SDKs can now return optional metadata fields, namely:
createdAt
updatedAt
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.
Rate this page: