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.
As previously announced, invocations from Forge apps that haven’t been updated since Jan 1, 2023 will now be blocked. We’re implementing this to ensure that all apps and customers continue to receive crucial fixes and security updates.
If your app hasn’t been updated since Jan 1, 2023, you’ll need to re-deploy your app to prevent its invocations from being blocked.
Additionally, the legacy runtime will be completely deprecated on Feb 28, 2025. As such, we strongly encourage you to migrate your app to the latest runtime before then.
UI modifications, the Forge module that allows apps to modify fields, now supports the original estimate field on the Issue transition view.
For more information, see the list of supported fields for Issue transition.
A new RFC is ready for review at : RFC-72 : Forge Object Store
The following Jira modules: global page, admin page, project settings page, and project page now support the changeWindowTitle method. Using the @forge/bridge API and the view object, you can set a custom title for the current document.
You can find the full documentation for this feature here: Forge bridge API.
The UI modifications (UIM) module now supports three new fields on the issue create modal:
due date field
target start custom field
target end custom field
The complete list of supported fields is available here.
We’re happy to introduce new Jira Software Forge product events for boards:
board created - avi:jira-software:created:board
board updated - avi:jira-software:updated:board
board deleted - avi:jira-software:deleted:board
board configuration changed - avi:jira-software:configuration-changed:board
Follow the link above to read more about them.
Following its EAP, we are excited to announce that the improved alerting experience is now generally available.
We have migrated the alert rules for apps that triggered at least one alert in the 90 days from Jul 16, 2024 to Oct 10, 2024.
For apps that had an alert rule migrated, app admins can edit these alert rules. App admins can also create new alert rules. For all apps that did not have an alert rule migrated, we recommend creating at least one alert rule to help you and your team proactively monitor your app's performance.
If you would like to share your feedback, you can use the “Give feedback” button located in the “Get help” section on the top right of the developer console.
We’re happy to introduce new Jira and Jira Software Forge product events for the following entities:
Project moved to trash - avi:jira:softdeleted:project
Sprint created - avi:jira-software:created:sprint
Sprint started - avi:jira-software:started:sprint
Sprint updated - avi:jira-software:updated:sprint
Sprint closed - avi:jira-software:closed:sprint
Sprint deleted - avi:jira-software:deleted:sprint
Follow the links to read more about them.
Rollout: This change will be applied to all sites over the coming weeks.
The issuelink_created and issuelink_deleted webhook events, where style is jira_gh_epic_story or jira_subtask, are no longer available. This follows the previous deprecation notice (see Change 5). We recommend using the parent field from the jira:issue_created or jira:issue_updated events instead.
Note: All other issuelink_created and issuelink_deleted webhook events are still available.
The Jira and JSM cloud navigation changes as previously mentioned are now available in EAP. This Early Access Program will enable partners to test the new navigation and assess how apps will adapt to the proposed changes.
As part of EAP, we’ve set up a dedicated group on CDAC where you’ll be able to discuss these changes. Please note that the designs in the EAP are not final, so you are NOT expected to make any changes to your apps during the EAP. For partners who previously expressed interest, the new navigation will be activated to the test instances today.
To join this Early Access Program, register using the EAP form.
See RFC-45 for more information on Jira and JSM Cloud navigation changes
We removed the properties API from the @forge/api package. This API was deprecated on Nov 1, 2023.
We’re pleased to announce that Jira now supports UI modifications for screen tabs. See the documentation for screen tabs for more details.
We’re pleased to announce that Jira now supports multiple concurrent UI modifications apps. This means that up to five UIM apps can now run for a given combination of project, issue type, and view type. See the documentation for Multiple UIM apps for more details.
Forge SQL is now available as an Early Access Program (EAP) feature, allowing developers early access to test SQL hosted storage functionality for their Forge app and provide feedback.
Refer to Forge SQL documentation for more information about the EAP.
To signup to the EAP, please use the request form.
We’ve added a new REST endpoint that allows you to fetch configurations for multiple Forge custom fields at the same time.
Rate this page: