Last updated Dec 12, 2024

Changelog

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.

12 December 2024

Announcement Workflow modules migration from Connect to Forge

You can now migrate existing Connect workflow modules to their Forge counterparts that are currently in Preview, with GA expected on those modules in Q1 2025.

This change allows your app to upgrade its existing Connect workflow modules to Forge modules. When upgrading, ensure that you set the Forge module key to the value of the key of the Connect module so that the Forge module can access existing workflow configuration information.

See Migrate Jira modules from Connect to Forge for more information.

More details

Keep in mind that the Connect and Forge modules offer different properties, and some of the Forge features are not available in Connect. For details, refer to the detailed module documentation (e.g., workflow validator Connect and Forge documentation).

Added Introducing UI Kit ADF Renderer component in preview

The AdfRenderer component provides a way to render a valid ADF document, using the same renderer that Atlassian uses internally to render ADF content in Confluence pages, Jira work items, and so on. See ADF renderer for the full docs.

More details

The ADF renderer component also allows you to replace node types that are unsupported in the context of a Forge app with replacement content, or remove them entirely.

See Atlassian Document Format for information on valid nodes.

Run npm i @forge/react@latest to install the preview version of the components and try them out now.

Added Introducing the event filtering expression playground

Developers can now use the Expressions playground to see if expressions used for event filtering correctly filter out https://developer.atlassian.com/platform/forge/events-reference/ sent to their Forge apps.

You can read more about the playground in our documentation.

11 December 2024

Deprecation Notice Nodejs18.x runtime

From Jun 30, 2025, the nodejs18.x runtime will be deprecated, impacting app deployments.

You must update your apps to use the newer nodejs20.x or nodejs22.x runtimes.

This is due to the Node.js version 18.x end-of-life scheduled for Apr 30, 2025.

Announcement New Jira Forge product events for components and issue types

We’re happy to introduce two new Jira Forge product events:

  • Component deleted - avi:jira:deleted:component

  • Issue type deleted - avi:jira:deleted:issuetype

Follow the links to read more about them.

Announcement Forge runtime now supports Node 22

Forge’s native Node runtime now supports Node 22.

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

Announcement forge eligibility command in Forge CLI version 10.13

We've added a new command forge eligibility that allows you to check the eligibility of your Forge app against predefined programs, such as Runs on Atlassian.

You can also check the eligibility of previous major versions of your app by using the --major-version flag.

To know more about the Runs on Atlassian program, visit https://go.atlassian.com/runs-on-atlassian.

To check if your app is eligible for Runs on Atlassian, go to the Forge CLI documentation.

Announcement Introducing Runs on Atlassian

We’re introducing a new program Runs on Atlassian as a Preview on Forge.

The program helps customers identify Forge apps that have no data egress and use data residency-enabled storage on the Atlassian Marketplace via a Runs on Atlassian badge.

To know more about the Runs on Atlassian program, visit https://go.atlassian.com/runs-on-atlassian.
To check if your app is eligible for Runs on Atlassian, go to the Forge CLI documentation.

Eligibility requirements may change leading up to the launch of the program.

9 December 2024

Added Forge linter now displays more detail for compilation errors

The forge lint and forge deploy commands will now output filename, index, line, and column numbers (if available) when an error occurs during compilation.

Added UI modifications now support the cascading select field on Global issue create

UI modifications, the Forge module that allows apps to modify fields, now supports the cascading select field on the Global issue create view.

For more information, see the list of supported fields for Global issue create.

Request for Comments (RFC) RFC-78: Dropping support for React 16 and rendering in a React 18 concurrent root in Jira and Confluence

5 December 2024

Removed  UI Kit @forge/react version 9 has been retired

We have now removed the UI Kit @forge/react version 9 from the Forge platform. This UI Kit version was deprecated on Aug 28, 2024.

We recommend using the latest version of UI Kit (@forge/react10).

For more information, see our deprecation policy.

Announcement Forge rich-text bodied macros available in preview

We're announcing a preview of rich-text bodied macros for Forge, allowing apps to define Confluence macros with a body in their manifest.

This also allows Connect apps to migrate their rich-text bodied macros to Forge.

Get started by checking out the macro module reference, or our tutorial on using rich-text bodied macros.

More details

Rich-text body macros let users insert rich content, like images and tables, within a macro using the Confluence editor. Apps can access and render this content within their macros. Macros using a custom editor can also provide an initial macro body on the first macro insert.

To be able to deploy these changes to your manifest, you will need the latest version of the Forge CLI. Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.

To learn more about migrating Connect macros to Forge, see https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-macro/.

Announcement Forge custom config editor for macros available in preview

We’re announcing a preview of custom config editors for Forge macros, allowing you to use a UI Kit or Custom UI resource for your macro’s configuration experience.

This gives you greater control over the presentation of configuration to the user and more flexibility with the storage of configuration properties.

Get started by checking out the macro module reference, or our tutorial on adding custom macro configuration.

More details

The custom macro configuration will be rendered in a modal overlaying the page, offering a larger canvas for more complex configuration scenarios.

Macros using a custom config editor can also provide an initial macro body on the first macro insert.

To be able to deploy these changes to your manifest, you will need the latest version of the Forge CLI. Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.

Added Local time zone available in the developer console

Developers can now view timestamps in the developer console according to their local timezone, as set in their device's operating system. This update allows developers to easily correlate incidents and activity with their specific time zone.

Previously, all timestamps were displayed in UTC. Developers can switch between their local time zone and UTC via the Profile menu in the top-right corner of the developer console.

Rate this page: