Rate this page:
This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.
Posts are made in the Forge announcements category of the developer community when the changelog is updated. Subscribe to the Forge announcements category to get notifications.
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.
In addition to existing events related to Confluence pages, blogposts, tasks, and comments, Forge apps can now subscribe to Confluence space events. For historical reasons, they all have a :V2 suffix:
Created: avi:confluence:created:space:V2
Updated: avi:confluence:updated:space:V2
See examples and payload information here.
Jira custom field and custom field type modules are now available on the new create issue dialog.
See Jira custom field and Jira custom field type documentation for more details.
We’ve introduced a new Forge module type confluence:global-page.
For more details, see Confluence global page.
We’ve released a fix for https://ecosystem.atlassian.net/browse/FRGE-212. Forge apps and Connect on Forge apps can now access restricted APIs by defining additional scopes in their manifest. In order for the correct scope behavior to take effect, Forge apps with existing scopes will need to do a major version update. If you are building a new app or adding new scopes to an existing app, scopes can be added to the manifest and deployed. The scopes will be synced with the next installation/upgrade.
We’ve added a new Jira event for custom field context configuration that provides information when the configuration is updated.
See the Jira events reference documentation for more details.
The home page in Confluence Cloud is receiving an update. This change modernizes the home UI, provides detailed views of your recent work, and improves the activity feed. We will begin the release on Dec 15, 2021 and hope to complete the rollout by the end of March.
This update includes changes to the right panel. You should confirm that the UI changes don't cause visual issues to Forge apps using the confluence:homepageFeed module and Connect apps using the webpanel atl.dashboard.secondary. To assist with checking and making changes, the home page update is available to the ecosystem beta group.
See Confluence Cloud home is getting an update for more information.
This change enables Forge apps to call an external OAuth 2.0 API using the fetch function with authentication handled by the Forge platform.
We’ve added the withProvider API to the @forge/api package.
The forge lint command now supports external authentication.
See the Use an external OAuth 2.0 API with fetch guide for more information.
Jira Cloud adds support for the project settings page module. This module adds an item to the project settings sidebar. When the item is clicked, content is rendered on a new Jira page. Use the UI kit or custom UI to create content for the Jira page.
This module can be used in Jira Core, Jira Software, and Jira Service Management.
Run npm install @forge/ui@latest on the command line in your app directory to install the latest
version of the UI kit.
Jira Cloud adds support for a global page module. This module adds an item in the Apps section of the main navigation. When the menu item is selected, content is rendered on a new Jira page. Use the UI kit or custom UI to create content for the page.
This module can be used in Jira Core, Jira Software, and Jira Service Management.
Run npm install @forge/ui@latest on the command line in your app directory to install the latest
version of the UI kit.
We’ve added new Jira events for custom fields. These events provide information on the creation, update, trashing, restoration, and deletion of custom fields and creation, update, and deletion of custom field contexts.
See the Jira events reference documentation for more details.
In version 2.0.6 of the CLI, we’ve fixed a bug related to the forge lint --fix command that was failing for missing permissions in the app manifest.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
The field and query param contextId in the Issue custom field configuration (apps) operation is deprecated and replaced with:
id, the ID of the configuration entry, which behaves in the same way as the deprecated contextId. Note, this is not the ID of the field context the configuration is associated with, contrary to the previous name.
fieldContextId, a reference to the field context ID the configuration is associated with.
The reason for this change is that while contextId was intended to be a reference to a field context ID, in some cases it wasn't. fieldContextId serves this purpose now.
The straightforward way of updating your app is to replace contextId with id, making everything work the same as before. However, do check whether fieldContextId is the field that you should use instead.
The contextId field and query param will be removed on 1 March 2022.
Jira custom field and custom field type modules now support the new datetime data type. This enables the usage of dates with both time and timezone in both modules.
See Jira custom field and Jira custom field type documentation for more details.
The following Jira modules can now access their issue’s typeId:
In Forge CLI version 2.0.5, we’ve updated the manifest validation to detect duplicate module keys.
This means that the duplicate keys in the following example are now detected:
1
2
3
4
5
6
7
modules:
webtrigger:
- key: webtrigger
function: webtrigger
function:
- key: webtrigger
handler: webtrigger.runRun npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.