ADDED - Navigate and open methods for custom UI apps in Jira
Custom UI now supports navigating to external links with the new router object exported from the
This object contains the
open(url) methods, which allow the app to open an external link. navigate opens the link in the same tab, while open opens the link in a new tab. Currently, these methods are only supported in Jira. See custom UI bridge for more details and examples.
npm install @forge/bridge@latest in your resource directory to update to the latest version.
ADDED - Jira project page module in UI kit version 0.12.0
Jira Cloud now supports the Project page module. The
jira:projectPage module adds an item in the Apps section of the left navigation of Jira classic project settings. When the item is clicked, content is rendered on a new Jira page. You can use the UI kit or custom UI to create the content for the Jira page. In the app, use the ProjectPage component as a top-level component.
This module can be used in Jira Core, Jira Software, and Jira Service Management.
Run these commands to install the following latest versions:
npm install @forge/ui@latestin your app directory on the command line to install the latest version of the UI kit
npm install -g @forge/cli@lateston the command line to install the latest version of Forge CLI
ADDED - Forge product events now support scopes
When using product events, your Forge app must now have permission from the site admin to access the data it provides within the event payload. The OAuth scope required is documented under each product event. Note, running the
forge lint command picks up these required scopes.
BUG FIX - in Forge CLI version 1.3.0
In this release:
- Missing OAuth scopes for trigger events are now detected by the linter, and are reported as errors.
- Error messages for deployments and installations have been improved.
npm install -g @forge/cli@latest on the command line to install the latest CLI version.