Changelog

You can now deploy Forge app builds directly via the developer console.

1. Selecting Deploy build from the actions menu next for the build you want to deploy.

2. Select the environment to which you’re deploying the build to.

Note, app build deployment permissions adhere to the existing permission structure for app contributors.

We have fixed an issue in how compute usage was calculated for async events and scheduled triggers in Forge apps.

This change was rolled out progressively between Dec 17, 2025 and Dec 19, 2025. As a result, affected apps may now report higher compute usage than before. This reflects more accurate tracking of the resources consumed; there is no change to the actual behavior or performance of your apps.

If you have alerts, monitoring, or internal reports based on Forge usage metrics, you may want to review them to account for this correction.

Logs automatically generated by the Forge platform during remote invocations (not logs generated by the app itself) are removed. The following platform-generated log statements are impacted:

• Making remote request: When remote invocation is triggered

• Successful remote request: When remote invocation was successful

• Failed remote request: When remote invocation fails

These logs will no longer be visible on the logs page in the developer console or in the logs CLI command. As a result, they are excluded from usage calculations and billing.

Developers utilising Forge remote will notice a reduction in their logs usage starting today.

To maintain visibility into remote invocations, we will be introducing success and failure information via metrics in the near future.

You can now use UI modifications with Jira Service Management (JSM) request create portal view. This is an extension of the existing jira:uiModifications module, allowing you to change the look and behaviour of JSM request create portal view. The module is designed to be used in conjunction with the UI modifications (apps) REST API.

For more information, see the JSM UI modifications module documentation.

Support for response streaming is now available in Forge LLMs. The new stream function in the @forge/llm SDK allows apps to process outputs as they are generated rather than waiting for the complete response.

Forge LLMs remain in Early Access (EAP). Due to high demand, participation is limited. To request access, join the waitlist here.

As part of the Forge platform pricing effective from Jan 1, 2026, we have introduced usage alerts. Developers will automatically receive notifications when the usage of any billable capability in the Forge app reaches key thresholds— at 50%, 75%, 90%, and 100% of free monthly usage allowance.

The following UI Kit components are now generally available:

• Comment, which displays discussions and user feedback.

• Pressable, which is a primitive for building custom buttons.

• CommentEditor, provides a contained comment editor UI with a simple toolbar.

• ChromelessEditor, provides a simple text editor that does not have a toolbar.

For more information, see the component documentation.

Currently, the new workflow editor is the default editing experience in Jira and is being used by the majority of customers.

Starting 26th June 2026, we will begin removing the old workflow editor for customers, which means workflows will only be editable in the new workflow editor. We ask you to please help your customers in this transition by ensuring that any workflow-related apps will work effectively with the new workflow editor.

If you encounter any issues with how your apps behave in the new workflow editor, please raise a support ticket.

Forge usage invoices for December 2025 will be generated on January 1st, 2026, and all usage during December is fully discounted. This allows you to experience the complete billing flow, including adding a payment method, reviewing usage, and receiving an invoice, before Forge pricing changes take effect on 1 January 2026. See the Atlassian blog for more details about the upcoming pricing changes.

This release includes:

• Developer Spaces
  A Developer Space is your team’s shared space for building, managing, and billing Forge apps. It brings together your apps, team members, and billing access in one place, making it easier to collaborate and organize your portfolio. Learn more in Introduction to Developer Spaces.

• Create Developer Spaces from the Forge CLI
  By using the CLI version 12.9.0 or above, 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.

• Billing experience
  You can now experience the complete billing journey for a Developer Space—from adding a payment method to receiving a fully discounted invoice for December 2025 usage. This helps you familiarize yourself with the process before pricing takes effect from January 1st, 2026 onwards. Learn more in Billing and payments in Developer Spaces.

• Resource usage API
  Use the new Export app resource usage API to access detailed resource usage data and integrate it with your own reporting or third-party tools.

• Commerce APIs
  The offering ID for Forge App Hosting is 59f614dc-f9d0-4fad-924d-bb9d707d33ab. Commerce public APIs can be leveraged for more information. These APIs can help extend your usage insights to cost-based insights.

• Expanded site-level usage visibility
  The previous limit of viewing only the top 20 sites for resource usage has been removed. You can now view all sites that generated usage for a resource in the developer console.

Key documentation updates

1. Forge Service Level Agreement is now available.

2. The Atlassian Developer Terms and Forge Terms have been updated with Payment, Billing and SLA details.

The requestRemote bridge API now supports passing FormData in the body of the request.

For more details, refer to the documentation for requestRemote.

Forge’s native Node runtime now supports Node 24.

To use this runtime, set your app.runtime.name to nodejs24.x in the manifest file.

We’ve added the module bitbucket:workspacePersonalSettingsPage to Forge. You can use this module to build a custom workspace settings page. For more information, see Bitbucket workspace personal settings page.

Following the Preview release, the forge build command is now generally available. You can use this command to bundle and upload builds of your Forge app and deploy them across multiple environments.

App builds created using this command are also visible in the Forge Developer Console under Builds.

For more information, see the Forge build command documentation.

Following its EAP release, Forge bridge rovo API is now available in preview.

The Forge bridge rovo API contains the rovo.open method, which allows you to open the Rovo chat sidebar and create a new conversation with either a default or specified Rovo agent.

Run npm install @forge/bridge@latest on the command line to install the latest version of @forge/bridge and receive these changes.

For more information, see the Rovo documentation.

You can now use UI modifications with the Project Picker field (com.atlassian.jira.plugin.system.customfieldtypes:project) in Jira. This enhancement allows you to customize the Project Picker field in the following views:

• Issue view

• Global issue create

• Issue transition screens

This update makes it easier to tailor the user experience when working with project fields across key Jira workflows.