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 products, 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.
This feature will allow Connect apps to move to Forge and existing Forge apps to offer data residency - realm pinning for remotes.
We've introduced the bitbucket:repoCodeOverviewPanel Forge module. This module adds an expandable panel on the Source page of a repository to display custom information defined in a Forge App.
This enhancement allows developers to customize the information displayed in the repository Source page, improving the visibility of critical data. For more information, see Bitbucket code overview panel.
User-Defined Remotes is now being considered as a future improvement to the developer platform. If this is of interest watch this roadmap item for updates. See https://ecosystem.atlassian.net/browse/ROADMAP-99 for more information.
We’re happy to introduce a new Jira Forge product event:
configuration changed - avi:jira:changed:configuration
Follow the link to read more about it.
With the recent updates to our content delivery network (CDN), all Custom UI apps now allow-list the Atlassian emojis API URL by default. This means you no longer need to declare egress to load images coming from the emojis API in Custom UI apps.
These recent updates can effectively help you reduce egress from your Custom UI apps.
These updates can help if you’re looking to make your app eligible for the Runs on Atlassian badge. To know more about Runs on Atlassian, see this developer blog post.
Note, the removal of egress does not require a major version update of apps.
Look for opportunities to remove the following external permissions from your manifest:
1
2
3
4
permissions:
external:
images:
- *.atl-paas.netFrom Jan 6, 2025, the use of web triggers will exclude apps from the Runs on Atlassian eligibility criteria.
This is because Forge web triggers currently allow for the egress of customer data returned in response to third-party requests.
While we understand that using web triggers is unavoidable for some use cases involving external systems, we’re also looking to uphold the integrity of the Runs on Atlassian badge for customers.
Eligibility requirements may change leading up to the launch of the program.
Many apps use bodied macros to allow Confluence users to add rich Confluence content inside of them while editing a page. Then, when the user publishes the page, the app applies formatting to the content and renders it in a “display” state on the published page.
Since live pages are designed to not need to be published, we have added a way to see a bodied macro’s “display state” directly while editing. Now, you can switch between bodied macros “editing” and “display” with a simple click in live pages. See More details for a GIF example.
With the recent updates to our content delivery network (CDN), all Custom UI apps now allow-list the Atlassian media API URL by default. This means you no longer need to declare egress to load images coming from the media API in Custom UI apps.
Unsplash images now load by default as well, so you no longer need to include the images.unsplash.com egress permission from Custom UI apps.
These recent updates can effectively help you reduce egress from your Custom UI apps.
These updates can help if you’re looking to make your app eligible for the Runs on Atlassian badge. To know more about Runs on Atlassian, see this developer blog post.
Note, the removal of egress does not require a major version update of apps.
Look for opportunities to remove the following external permissions from your manifest:
1
2
3
4
5
permissions:
external:
images:
- images.unsplash.com
- api.media.atlassian.comWe’re happy to announce several improvements to the JQL Functions module as well as the related precomputations API:
New endpoint to fetch precomputations by ID; see the docs to learn more.
New param (skipNotFoundPrecomputations) for the Update precomputations endpoint, allowing the request to succeed even if some of the requested precomputations no longer exist.
The same endpoint now returns a list of IDs of precomputations that couldn’t be found - notFoundPrecomputationIDs.
Apps can now return the storeErrorAsPrecomputation param to store the error message as a precomputation , see https://developer.atlassian.com/cloud/jira/platform/jql-functions/#output.
We have added four new Forge modules in Jira, which provide additional extension points for customizing and extending Jira functionality.
The following modules are available in Preview:
Module | Description |
|---|---|
Adds a menu item to the more actions (•••) menu for the Jira backlog view. | |
Adds a menu item to the more actions (•••) menu for the Jira board view. | |
Adds a menu item to the actions (•••) menu on a sprint card in the backlog view. | |
Adds an item to the user's profile menu in the main navigation. When the item is clicked, content is rendered on a new Jira page. |
To be able to use the new modules, you must first update the Forge CLI: npm install -g @forge/cli@latest
These new Forge modules also allow Connect developers to replace equivalent Connect modules. For details on these equivalents, see Connect module equivalents.
The environment key is now included in the URLs for the following modules:
Note: You will need to update any bookmarks or saved links to these pages to view your Forge app in the left navigation.
For example, for repoMainMenuPage the URL path is changing per below:
from: /{workspaceSlug}/{repositorySlug}/forge/{forgeAppId}/{forgeAppModuleKey}
to: /{workspaceSlug}/{repositorySlug}/forge/{forgeAppId}/{forgeEnvironmentKey}/{forgeAppModuleKey}
The page loaded directly with the old URL will no longer have menu items on the left navigation:
To navigate to the new URL:
Select the breadcrumb link (test_repo1 in the screenshot above) to load the repo page.
Select the menu item for the Forge page on the left navigation.
All your apps will now be listed on the left navigation.
Following the EAP release, UI Kit’s Frame component is now in preview. This means you can use the Frame component in the production environments.
The Frame component allows you to load custom resources within UI Kit, making it easy to import non-UI Kit components in a UI Kit module.
This update also supports Frame across all modules for Jira, Confluence and Compass.
For more information about how to use the Frame component, see here.
To use the latest version of the Frame component in your UI Kit app, install the @forge/react latest version by running npm install --save @forge/react@latest
We've introduced the bitbucket:repoPullRequestOverviewPanel Forge module. This module adds an expandable panel on the PR Overview tab to display custom information defined in a Forge App.
This enhancement allows developers to customize the information displayed in pull request overviews, improving the visibility of critical data. For more information, see Bitbucket pull request overview panel.
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.
Rate this page: