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 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.
Bitbucket Data Center and Server 8.19.23 and 9.4.11 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
We've rolled back the Developer Spaces feature for Forge apps in the Developer console and Marketplace. We're taking this step to gather more feedback and improve the experience before making it generally available again.
If you started using Developer Spaces, your apps and team settings will revert to the previous experience. If you made changes to your team structure or roles during this period, review your team setup and adjust as needed to match the previous configuration.
We'll share updates and a new release date soon. To provide feedback or learn more, see the original September 3, 2025, changelog or the Community.
We are releasing a Workflow Preview API that offers read-only access to workflow configurations. This API supports the current workflow view for work items within a project context. The preview includes nearly all the content of the full workflow but limits exposure of rule configurations and status properties. It is also available to users with View (read-only) workflow permissions.
We've updated our Forge documentation to refer to Jira, Confluence, and other Atlassian products as “Atlassian apps.” This shift in terminology—from “products” to “Atlassian apps”— is part of our effort to create a more unified and consistent experience across the Atlassian platform.
This terminology update does not affect APIs, app functionality, or how customers use or install apps.
For more information, see the community announcement Changing our terminology from “products” to “Atlassian apps”.
Forge CLI now offers AI-powered assistance through Rovo CLI and Gemini CLI. This integration allows the AI agent to analyze errors from Forge commands or tunnels and suggest actionable fixes automatically, enhancing your development experience. It connects with the app developer's existing Rovo and Gemini accounts; Forge does not provide an AI agent account but facilitates this integration.
This feature is experimental and opt-in. We may change or remove it at any time.
How to get started:
Install the latest Forge CLI (v12.5.0+): https://developer.atlassian.com/platform/forge/cli-reference/
Set up your preferred AI Agent:
Enable the feature with:forge assistant on rovo
orforge assistant on gemini
To turn off, run:forge assistant off
For more information, run forge assistant --help.
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-m0011.
This EAP release isn't for production or demonstration use.
We're releasing a set of space role APIs for Confluence instances that have opted into Role Based Access Control (RBAC). These APIs will allow you to create, update, and delete custom space roles. Custom space roles let you tailor access beyond Confluence's default space roles, making it easy to match internal workflows and ensure the right people have the right access.
Macro Autoconvert has be updated to allow custom URL schemes to be used as matchers for URLs. See the Macro Autoconvert docs https://developer.atlassian.com/platform/forge/manifest-reference/modules/macro/#macro-autoconvert
To use custom URL schemes in your matchers, you must first update the Forge CLI: npm install -g @forge/cli@latest
Bulk operation EAP has closed. The feature will be temporarily shutdown and evolved as we move the feature to GA.
We will not be accepting any new sign-ups to the EAP from Sep 3, 2025
The experimental SDK and corresponding API will no longer work
The GA version of the feature will have a different shape.
These changes have been rolled back. For more details, please see https://developer.atlassian.com/changelog/#CHANGE-2781.
We've launched Developer Spaces in the Developer console for Forge apps, providing a new way to organize your apps, team members, and billing in one place. All new Forge apps must now be created in a Developer Space, and existing non-marketplace apps must be linked to a space.
This release includes:
Admin role management: All members are space admins with full permissions to manage apps and team membership.
Developer Console integration: Manage spaces, apps, and team members, and use the space switcher to navigate between spaces.
App assignment and management: Assign existing non-marketplace apps to the appropriate developer space in the console. Marketplace apps are already linked to the developer space matching the marketplace partner account name.
CLI support: Updating the CLI to version 12.5.0, you can create Developer Spaces and assign apps via the Forge CLI during forge create or forge register workflows. Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
App transfer (manual process): Transferring apps between spaces requires a support ticket for non-marketplace apps or following the Marketplace transfer process for Marketplace apps.
Important changes to Marketplace publishing
Publishing apps to the Marketplace will now work differently, and it’s important to review these updates:
The list of publishable Forge apps is now based on Developer Space membership.
All Forge apps must be linked to a Developer Space before they can be published to the Marketplace.
Only Developer Space members with the appropriate permissions can publish apps.
These changes align publishing and billing responsibilities with Developer Space governance and prepare for the upcoming usage-based pricing model.
If you publish apps to the Marketplace, review your current apps and confirm they are linked to the correct Developer Space.
Known limitations:
Only the Admin role is available for this release. Additional roles and permissions will be introduced in the future. For anyone interested in more roles, please see the Jira ticket for feedback : https://ecosystem.atlassian.net/browse/FRGE-1893
App transfer between Developer Spaces requires manual intervention.
Some advanced governance and reporting features are not yet available.
For more information, see the Developer Space documentation.
The forge install command now features a new --major-version flag, which allows you to install a specific version of your app to a context. For example:
forge install --major-version 4
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@latestWe’re releasing a TypeScript bundler for apps through Forge’s Early Access Program (EAP).
Unlike the existing Webpack bundler, the TypeScript bundler enables the use of newer TypeScript versions and dependencies that may require data files such as native binaries or WebAssembly.
To join the EAP, please use the registration form here.
To use TypeScript, set app.package.bundler property in the app manifest to typescript. Afterwards, you can update the version of TypeScript in the application, and rely on application dependencies that require non-JS files to function.
See Packaging for more information.
Forge Cache EAP has closed. The service will not progress to GA, as we are shifting our investments to better address developer use-cases.
We will not be accepting any new sign-ups to the EAP from Aug 29, 2025
The EAP environment will be decommissioned and all cache data deleted after Sep 30, 2025
We are still committed to solving the underlying use-cases that led us to develop Forge Cache, taking what we’ve learned from the EAP and applying it to solutions that will offer better outcomes for developers.
Thank you to all of the EAP participants for helping us test Forge Cache and enabling us to build a better platform.
Over the past several months, we’ve been closely evaluating Forge Cache based on feedback from our developer community and partners, as well as broader strategic shifts within Atlassian. Here are the key factors that have shaped our decision:
Performance limitations: Forge Cache’s current performance (P90 of 20-30ms) does not meet industry standards for low-latency caching. This has been a consistent pain point for developers building latency-sensitive applications.
Missing developer needs: Many use cases require data persistence, dynamic or long TTLs, and advanced features like job queuing—capabilities that go beyond what a simple cache can provide.
Multi-cloud strategy: Atlassian is investing in a multi-cloud strategy, with deployment options to isolated cloud, government cloud and Google Cloud Platform. Achieving the low latency expected from a cache is only possible once Forge Functions and Forge Containers are supported within the same cloud platform, which is not feasible in the near term.
Given these factors, we have decided not to progress Forge Cache to General Availability (GA). Instead, we are shifting our investments to better address the broader developer needs:
All timelines are indicative and subject to change.
Q2 FY26:
Forge KVS Enhancements: We will introduce new capabilities such as Conditional SET with TTL. Transactions for KVS has already shipped, enabling atomic operations.
Q3–Q4 FY26:
Performance Improvements: We are targeting Forge KVS performance to reach a P90 of 40–50ms, narrowing the gap with Forge Cache.
FY27:
FIFO Queues: Launching a new FIFO Queues service to help developers queue jobs and break up large computations—addressing a top-requested feature.
Container-Based Compute Cache: We plan to invest in a new container-based compute cache, designed to deliver even faster performance and support advanced caching scenarios.
Forge Cache EAP will close: We will not be accepting any new sign-ups to the EAP from Aug 29, 2025. The EAP environment will be decommissioned and all cache data deleted after Sep 30, 2025.
Forge Cache will not move to GA. We recommend to evaluate use of Forge KVS for your use case.
Feature Parity: We are working to ensure that Forge KVS and the new services will cover the majority of use cases previously addressed by Forge Cache, with additional benefits like data persistence and transactional support.
We understand this decision may be disappointing to some users, however, we believe it is the right strategic path for Forge. We are still committed to solving the underlying use-cases that led us to develop Forge Cache, taking what we’ve learned and applying it to solutions that will offer better outcomes for developers.
As we progress with above roadmapped improvements, we will provide updates on developer community, Forge changelog and on our public roadmap.
To support Jira performance at scale, we are introducing a limit on how many work types and how many fields can be associated to a company-managed project in Jira cloud:
The admin user interface and related APIs will restrict the association of more than 150 work types to a single work type scheme.
Similarly, they will also limit the association of more than 700 fields within the single field configuration scheme.
The limit will be effective starting Feb 9, 2026.
Exemption which will be allowed to go over these limits. Examples include:
Installing a new app
Enabling a new product
Upgrading (or downgrading) a license tier
Creating a new project
Migrations
Jira Admins will have access to streamlining tools designed to eliminate unused fields and work types. This initiative aims to ensure that the field configuration scheme and work type scheme remain within the established limits.
Support documents
This is building on top of what we announced in https://community.atlassian.com/forums/Jira-articles/Announcement-Changes-to-field-and-work-type-configuration-in/ba-p/3023478
Fields https://support.atlassian.com/jira-cloud-administration/docs/optimize-fields-in-your-project/
Work types https://support.atlassian.com/jira-cloud-administration/docs/optimize-work-types/
The following APIs will be impacted:
Add work type to a work type scheme: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-type-schemes/#api-rest-api-3-issuetypescheme-issuetypeschemeid-issuetype-put will return HTTP 400 if the scheme is over a limit
Create issue type scheme: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-type-schemes/#api-rest-api-3-issuetypescheme-post will return HTTP 400 if the issue type count is over a limit
Assign work types to field configurations: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-field-configurations/#api-rest-api-3-fieldconfigurationscheme-id-mapping-put will return HTTP 400 if the scheme is over a limit
Team-managed projects already have their own limits:
There is a limit on how many work types can be in a team-managed project: https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/ this limit remains unchanged
There is a limit on how many project scoped fields can be created in a team-managed project: https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/. The amount of global scoped fields is unlimited. This will change so that team-managed projects will now observe the same limit of fields as company-managed projects.
Rate this page: