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.
Rollout: Progressive rollout by tenant. IMPLEMENTING
Updating workflows via the Bulk update workflows API will discard existing draft workflows that are associated with the workflow.
This change is being made because draft support will be discontinued with the retirement of the old workflow editor.
We are removing documentation for internal APIs from public docs for graphql APIs (from Connect Service section). These APIs are meant to be used by Atlassian experiences only and we do not support these APIs for public consumption.
The APIs for which docs are removed are:
Atlassian previously announced that customer general availability (GA) for multi-instance pricing would move to the fourth quarter of 2025. We are pleased to share that, while GA is still planned for Q4, we have launched a closed Early Access Program (EAP) with customers. This EAP will help us ensure we deliver a high-quality, robust feature.
In order to help Marketplace Partners accommodate larger customers, Marketplace cloud app pricing will be adjusted to match parent product pricing. We increased the number of users that customers can license on Jira Cloud from 50,000 to 100,000 on Jun 26, 2025
Beginning Jul 9, 2025, the pricing tiers for Jira cloud apps will be increased up to 100,000 users, a 100% increase from the previous limit of 50,000 users, with the following new pricing tiers added: 50,001 - 60,000 60,001 - 70,000 70,001-80,000 80,001-90,000 90,001-100,000 .
Transactions for KVS and Custom Entity Store is now generally available (including its REST API).
This feature allows multiple operations in a single transaction, ensuring that all operations are either committed or rolled back together if one fails. When used in the Custom Entity Store, you can add conditions to operations.
While version 3 of the Marketplace Review APIs is still under development, we’re releasing the documentation for these reporting 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.
Description:
Bitbucket Data Center and Server 8.19.20 and 9.4.8 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
A Confluence 10.0 beta version is available now for testing. To find out what’s changed, check out Confluence 10.0 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.
You can now declare a default value for environment variables in your manifest, which will be used if no environment variable is already exported. Read more about Variables.
We’ve increased the maximum number of resources that can be bundled with an app from 10 to 50. For more details, you can refer to the Forge resource limits.
We’re sharing a guide that explains how to improve page load by managing Web Resource Manager (WRM) and Custom App Dependencies.
In Jira, WRM is responsible for preparing JavaScript and CSS resources for specific pages to ensure apps function correctly. When creating an app, you define its dependencies in <web-resource> and specify the context where your app will run in Jira. Then, WRM generates batch.js and batch.css files by collating all required dependencies for apps running in that context.
Depending on the context registry and how dependencies are defined, these batch files can become very large, leading to slow page load performance. However, you can improve the page load by:
Code splitting
Deferring script loading
Compressing files
Further optimization for custom apps
A new RFC is available for review at https://community.developer.atlassian.com/t/rfc-99-upcoming-changes-to-bitbucket-navigation/93702.
As of Jul 7, 2025 , the following APIs will stop returning usage data in their responses:
Workflows
Statuses:
Workflow schemes:
Refer to CHANGE-2298 for more details.
The CLI linter was incorrectly adding an optional property to some existing egress permissions when it identified that certain permissions were defined using the simple string format.
This issue resulted in the manifest file being altered from:
1
2
3
4
5
permissions:
external:
fetch:
backend:
- 'test.com'to:
1
2
3
4
5
6
permissions:
external:
fetch:
backend:
- address: 'test.com'
inScopeEUD: falseThe latest version of the CLI fixes this problem and does not populate the optional inScopeEUD property anymore.
To install the latest version of @forge/cli and access these improvements, run the following command in your terminal:
1
npm install -g @forge/cli@latestTo join this Early Access Program, please complete the Forge EAP sign-up form.
The Confluence Full Page UI module aims to enable developers to build fully custom, chromeless app experiences within Confluence Cloud, hosted directly on Forge.
To start using this EAP, sign up using the Forge EAP form.
For more information about how to use this module, see here.
Rate this page: