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.
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.
We updated our published IP addresses and domains for Atlassian cloud products to include IP address ranges for outbound connection for Forge apps.
You can use these IP address ranges to allow Forge apps to make connections through firewalls or integrate with software that has a managed IP allowlist.
Note: Per-app IP allow listing is not supported
The IP address range for outgoing connections is shared by all Forge apps. Allowing connections from this IP address range will permit connections from any Forge app.
Forge apps currently use the following IP address ranges for outbound connections:
1
2
3
4
5
6
7
8
18.236.52.165/32
34.215.254.205/32
35.160.6.102/32
52.43.192.52/32
52.89.100.78/32
54.190.195.254/32
54.214.155.219/32
54.218.196.28/32If you plan to use these IP address ranges, it’s important that you monitor Atlassian’s documentation for changes to this range. A JSON file containing this information is published to https://ip-ranges.atlassian.com/, which may aid automation.
Node Release 16.x has now reached its end-of-life. As such, the Forge CLI will no longer support systems running this version. You should upgrade to an LTS or Maintenance Node version (namely, 18.x or 20.x).
Read more about Node LTS version support here.
The route template function (used to access Atlassian product APIs) now blocks more potentially malicious user input; this helps prevent vulnerabilities like path traversal in Forge apps. We’ve implemented this enhanced security through additional checks that only apply to the path segment of the URLs being constructed (not query strings).
If you are sure the input is legitimate and cannot lead to an unexpected API call, you can encode it manually or use assumeTrustedRoute.
We have added a new isSpaceAdmin display condition for Confluence. Now you can display your app modules only for space admins. This is available only for modules that are registered on space and page level.
See the display conditions for Confluence reference documentation for more details.
UI modifications, the Forge module that enables apps to modify fields, now allows you to create UIMs on the Global issue create modal for Jira Work Management projects.
For more information, see the list of supported project types for GIC.
We’re pleased to announce a preview release of support for a new location via the UI modifications extension point: Issue view.
It’s the second Jira location to be supported, following the initial support for the Global issue create modal.
Documentation specific to the Issue view is available under this link. The supported fields and methods are listed here.
To assign a UI modification to the Issue view context, you need to pass a viewType equal to IssueView while creating or updating the UI modification. See more details in our REST API docs.
At the same time, we’re ending the UI modifications Issue View Early Access Program. Your apps developed during the EAP will continue to work.
Apps enrolled in the Native Node.js runtime Early Access Program (EAP) can now use the Authorize API.
See the details below for instructions to use this API in your app.
To use the Authorize API in your app:
Upgrade your Forge CLI to the latest version by running npm install -g @forge/cli@latest.
Upgrade to the latest version of the @forge/api package in your app’s dependencies.
Re-deploy your app by running the forge deploy command.
Jira Cloud Platform features new workflow scheme APIs for company-managed and team-managed projects, allowing you to programmatically retrieve and update the details of workflow schemes. These new APIs are all declarative, allowing you to define the desired end state as well as system transitions from your current state to the desired state.
The new APIs are:
Bulk get workflow schemes: return a list of workflow schemes.
Update workflow schemes: update a workflow scheme.
Get required status mappings for workflow scheme update: get the required status mappings for the desired changes to a workflow scheme.
UI modifications, the Forge module that allows apps to modify fields, now supports the issue type system field for Global issue create modal.
For more information, see the list of supported fields.
We have now added Inline and Stack components in UI Kit 2. With these new layout components, you can easily organize your components either horizontally (Inline) or vertically (Stack).
For more information on how these components can be used with examples, see Inline and Stack documentation.
Run npm install @forge/react@latest --save on the command line to install the latest version of the @forge/react package.
Forge app logs are now available for apps enrolled in the Native Node.js runtime Early Access Program (EAP), removing one of the key limitations of the EAP. We are continuing to make progress towards production-readiness for the new runtime, which is forecast for later in 2023.
See the details below for instructions to enable logging for your app. To start testing out the improved compatibility and performance benefits of the new runtime in EAP, please fill out the registration form.
Upgrade your Forge CLI to the latest version by running npm uninstall -g @forge/cli; npm install -g @forge/cli.
Upgrade to the latest version of the @forge/api package in your app’s dependencies.
Re-deploy your app by running the forge deploy command.
Logs for your app should now be accessible when using the forge logs command or viewing logs in the developer console.
We are continuing to harden the logging infrastructure for the new runtime throughout EAP. For now, some limitations will apply the reliability of app logs:
There is a chance that some log statements may be displayed out of order.
There is a chance that some log messages may not be displayed if your function finishes executing before all log statements have been ingested.
If your function fails due to exceeding the 25 second runtime timeout, the log messages from that invocation will not be displayed.
These limitations will be addressed before the feature exits EAP.
We’re happy to introduce a new batch of Jira Forge events for the following entities:
Attachments (created)
Projects (created, updated, archived, unarchived, restored)
Components (created, updated)
Project versions (created, updated, released, unreleased, archived, unarchived, moved, merged)
Issue worklogs (created, updated)
Follow the links to read more about them.
You can now view the storage usage of your Forge apps across development and staging environments of sites where your apps are installed. This lets you manage your storage limits more effectively.
The dot menu is going to be replaced by the command palette in approximately 6 months.
Currently, the Jira Issue Action extensibility point is pulled into the dot menu. We won’t replicate this functionality in the command palette in the immediate term, but we're considering adding an explicit extensibility point in future iterations.
This change won’t impact your users' access to your functionality from the quick actions toolbar or the three dot menu in the issue view.
When migrating from Connect to Forge, running the forge register command now maintains the app.connect section of the Forge manifest. This ensures that the development of migrating apps continues to be a smooth experience.