Changelog

The extension context now includes navigation details that indicate whether a customer is viewing the new or old navigation system, represented by the structure { "jira": { "isNewNavigation": boolean } }, for all Jira Forge apps. This allows developers to customize their Jira Forge apps according to the type of navigation the customer is using.

We will not be issuing any new waivers for apps that need to request or store Atlassian user API tokens. This decision is part of our ongoing commitment to enhancing security and protecting customer trust.

Forge Apps that have already been granted waivers must ensure a lack of alternative solutions within Forge. They can continue to operate, but no additional waivers will be granted for new modules or new functionality within the same app.

Connect apps that have been granted waivers and any existing Connect app requesting or storing Atlassian user API tokens are required to migrate to Forge, with tokens stored in Forge encrypted storage.

With the recent updates to our content delivery network (CDN), all Custom UI apps now include the Atlassian emojis API URL in the allow-list by default. This means you no longer need to declare egress to fetch emojis in Custom UI apps.

These recent updates help you reduce unnecessary egress declarations from your Custom UI apps.

The fiveMinute scheduled trigger interval is now generally available (GA).

Developers can now use the scheduled trigger module to create scheduled trigger modules in a Forge app with intervals of fiveMinute, hour, day, and week.

For more information on using these intervals, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/scheduled-trigger/#scheduled-trigger module documentation.

We’ve added a new optional parameter openOnInsert to the configuration object in the manifest of Forge macros. This allows developers to control if the custom configuration modal is automatically opened when first inserted.

For more information, see Macro.

We have updated our UI Kit components, Text and Heading to make them more flexible:

Text

• Now supports align, as, color, maxLines, size and weight properties.

For more information, see Text component documentation.

Heading

• You can now control how the Heading component appears by setting a value for size, while the as prop controls the HTML element's rendering.

For more information, see Heading component documentation.

We are happy to announce we have added support for macro autoconvert to UI Kit. This allows your app to automatically insert a macro into the editor when a user pastes a recognized URL.

For more details, please see the Macro documentation.

Reminder: Starting Apr 30, 2025, a subset of Connect extension points will no longer be available on Confluence pages. For details, see the original deprecation notice linked below.

deprecation notice Deprecating a subset of Confluence page extension points

Action is required from developers using deprecated extension points.

We are pleased to announce that UI Kit component reference documentation is now embedded within the component source using JSDoc.

This enables developers to access component information directly from their integrated development environments (IDEs), improving the development workflow.

This is available for developers using @forge/react@11.1.0 or above.

The minimum compatible Node.js version for the Forge CLI has been updated to 18.20.7. Developers running older versions of Node.js will need to upgrade to this version or later to continue using the Forge CLI. This change ensures that all developers have access to the latest features, security updates, and performance improvements.

The app.version property in FIT contains a string used by some internal Atlassian services. As such, it does not accurately represent the actual app version. To refer to the correct Forge app version, use the new app.appVersion property instead.

The app.version property will be removed on Sep 25, 2025.

In the latest version of @forge/react, we're adding a new disableSubmitOnBlur property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value on blur events.

For more information on this component, see the component documentation.

The Forge SQL service’s cluster will be upgraded during a routine maintenance window on Mar 24, 2025 from 21:00 - 21:30 UTC. During this time, control plane operations (such as fresh installations or upgrade of an app that uses SQL capability) may fail intermittently. Data plane operations such as SQL queries will continue to work as normal. Other Forge storage capabilities will not be impacted during this maintenance window.

The Jira workflow validator function has been enhanced to provide additional details about fields that have been modified during a work item transition.

To see list of all supported field types, please refer to the documentation: Jira Workflow Validator.

After the beta phase of Atlassian’s new navigation, we’re thrilled to announce its General Availability (GA) for Jira, Jira Service Management, Jira Product Discovery, Confluence, and Atlassian Home. In this article, you’ll find key details about what’s changing with the new navigation, Jira and Jira Service Management apps, as well as when those changes will go live.