This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.
See what's next for Forge on our platform roadmap.
We're excited to share that Forge, our app development platform for Atlassian cloud apps, is now generally available. You can rely on Forge's hosted infrastructure, storage, and FaaS functions to support apps in production; all of which are backed by Atlassian's operational readiness. Learn more about building the next Marketplace hit with Forge.
Note that some functionality in Forge remains in beta while we're still making changes that may break your apps. Learn more about the current functionality in beta.
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'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”.
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.
Since our previous announcement about the analytics tool policy for Forge apps, we have received feedback from the developer community. Based on this feedback and customer requirements, we will explore a long-term solution that meets the needs of our mutual customers. As such, we are temporarily updating the analytics tool policy for Forge apps.
Effective 28 August 2025, we will allow tools with session recording features, script aggregators, and developer observability tools. While we explore long-term solutions, we will provide at least four weeks' notice before implementing any further changes to the policy.
As an app developer, please remember the Shared responsibility model and continue to prioritize customer data security.
Forge CLI now supports listing recent deployments using a new command, forge deploy list.
This command, by default, will show a table of the app’s recent deployments sorted by deployment date. It includes relevant details, including the environment and version, as well as the new “build tag” if the deployment was made using the forge build command. It also supports JSON output using the --json option, similar to other list commands in the Forge CLI.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli and receive these changes.
The ability to build a custom Teamwork Graph connector using Forge is now in EAP. Connectors allow you to ingest your app data into the Graph, associate it with Atlassian objects (for example, work items), and make the data available to customers in platform experiences like Chat, Search and Agents.
If you’re interested in joining the EAP, we recommend first checking the supported object types to see if we support your use case. Support for custom object types will come in a future release (2026).
To participate, please sign up for the EAP here.
The Forge CLI is now available via a development container for both VS Code and IntelliJ. It provides a consistent and isolated environment that is pre-configured with the necessary dependencies to build Forge apps.
To get started, follow this guide to install the necessary tooling and set up your environment.
We’re adding the capability to uninstall and upgrade Forge apps directly within your Bitbucket workspace settings. This means you no longer need to do these tasks in the Distribution screen of the developer console.
Note, the upgrade functionality is only available if the app has a more recent version available.
The Forge https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-panel/ module now supports options to show or hide a panel in all work items throughout a project.
These options dynamically appear in the panel’s action menu, depending on whether the panel is hidden or displayed in all work items. The action menu will show the Show for all work items option if the panel is hidden on all or some work items. Selecting this option will replace it with the Hide from all work items option. Both options will show/hide the panel on all work items throughout the project.
We’ve added new Confluence product events for entity deletions:
avi:confluence:deleted:page
avi:confluence:deleted:blogpost
avi:confluence:deleted:attachment
avi:confluence:deleted:custom_content
avi:confluence:deleted:space:V2
You can use these events to invoke your Forge app function when a page, blog post, attachment, custom content, or space is deleted. For more details see the Confluence events reference documentation.
Rate this page: