Last updated Jul 12, 2024

Changelog

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.

12 July 2024

Announcement Forge apps utilising the Connect `lifecycle` module will move to distinct secrets

On Jul 30, 2024, we will begin rolling out a fix for Forge apps which declare the Connect lifecycle module to use a distinct shared secret that changes on major versions instead of a single shared secret like it is currently.

The history of why we are making this change and why we want to move to this secret model is outlined here. If you’ve followed the previous post, we expect no functional changes for app developers. Please ensure your apps are storing and maintaining secrets on a per-installation basis.

  1. On Jul 30, 2024, new Connect on Forge app installations, major version upgrades, and Connect to Forge migrations will start receiving distinct shared secrets.

  2. After Aug 7, 2024, we will be rotating the secrets of existing Connect on Forge app installations to move them to distinct shared secrets. A new installation payload containing this secret will be shared.

These changes will be rolled out on a per-tenant basis.

11 July 2024

Announcement Forge tunnel now uses Cloudflare instead of ngrok

On Jul 8, 2024 we announced that we started migrating forge tunnel to Cloudflare from ngrok. As of today, all developers using forge tunnel on Forge CLI 10.1.0 have now been migrated to Cloudflare.

We strongly recommend that you upgrade to the latest CLI version (see Upgrading for more details). If you are using a firewall, you may notice new connections to Cloudflare's tunnel infrastructure. For forge tunnel to work, ensure these connections are allowed.

Older CLI versions will continue to use ngrok for forge tunnel (and, therefore, will still require an ngrok account). For more information, see Tunneling.

10 July 2024

Announcement Making interacting with and configuring macros easier in the Editor

Today, we are starting the gradual roll out of a new selection / configuration control for macros in the Editor that will make it easier to configure macros while editing in Confluence, starting with sites in the Developer Canary Program and a portion of users. No updates or work will be required by app makers.

To see this in action, check out More details below.

More details

Thanks to all who left feedback in the RFC!

9 July 2024

Removed `app.connect.authentication: oauth2` has been retired

Connect apps registered on Forge are no longer able to set `app.connect.authentication: oauth2` in their manifest. This caused client credentials to be sent in the installation hook that could be exchanged for an api.atlassian.com access token. Developers wishing to make requests to api.atlassian.com from their app server should use Forge Remote instead. If you were relying on this feature, we’re happy to answer questions you may have about migrating on the Developer Community forums.

8 July 2024

Deprecation Notice Planned change to the event schema for issue worklog Forge product events

We’ll be introducing a change to the schema of Forge issue worklog product events (created / updated).
Specifically, the author and updateAuthor fields of Worklog will no longer be mandatory.

To give you ample time to adjust, we're providing a 6-month deprecation period for the schema.
Therefore, the change will take place on Jan 8, 2025.

More details

The schema for the Worklog entity will change from:

1 2 3 4 5 6 7 8 9 10 11 interface Worklog { id: string; issueId: string; author: User; updateAuthor: User; created: string; updated: string; started: string; timeSpent: string; timeSpentSeconds: number; }

to

1 2 3 4 5 6 7 8 9 10 11 interface Worklog { id: string; issueId: string; author?: User; updateAuthor?: User; created: string; updated: string; started: string; timeSpent: string; timeSpentSeconds: number; }

making the author and updateAuthor fields optional.

Note that this means that the author and updateAuthor may be missing from the payload when a worklog is created or updated by an anonymous user.

Announcement Forge Tunnel migration with Cloudflare has begun

We will be gradually transitioning from ngrok to Cloudflare for the Forge Tunnel in the Forge CLI version 10.1.0 throughout this week. This migration means that the Forge Tunnel will use Atlassian-managed Cloudflare infrastructure, eliminating the need for developers to manage separate accounts, unlike with ngrok.

If you are using a firewall, you may notice new connections to Cloudflare's tunnel infrastructure. Please ensure these connections are allowed for tunneling to work. Older CLI versions will continue to use ngrok for Forge tunnels and will require the existing setup to be maintained. For more information, see tunneling.

5 July 2024

Added Forge remote is now available for Forge functions (preview)

Forge functions can now interact with remote backends utilising Forge Remote. This capability makes it simpler and more secure to integrate remote backends with your Forge app.

See Forge Remote - Calling a remote backend from a Forge function for more information.

4 July 2024

Added Forge tunnel now informs the user to deploy following manifest changes

Changing the manifest.yml in a Forge app while running forge tunnel will result in a notification that these changes will not apply until the app is deployed again. This is simply an improvement to the development experience and not a change in behaviour; tunneling and development of the application code can continue as usual until the decision is made to stop the tunnel and deploy the app.

28 June 2024

Early Access UI Kit data visualizations EAP

UI Kit data visualizations components are in Early Access Program (EAP).

We now have the following data visualization components to organize and present data:

  • Bar chart

  • Stack bar chart

  • Horizontal bar chart

  • Horizontal stack bar chart

  • Line chart

  • Pie chart

  • Single value

To start using this EAP, sign up using the Forge EAP form.
For more information about how to use the components, see here.

27 June 2024

Early Access Tunneling support and other updates for Forge Cache (EAP)

Forge Cache (EAP) now supports tunneling in the current Node.JS runtime. This will help improve the way you test and debug functions that use Forge Cache.

With this update, both incrementAndGet and decrementAndGet now support TTL (optional). In addition, we also standardised error codes that can help you automate better error handling in your app.

For more information, see Cache (EAP)

To start using and testing Forge Cache, please sign up using the form here. You can also join the group here to get regular updates, leave feedback, report bugs etc.

26 June 2024

Removed The `route` parameter is now mandatory for the `confluence:spaceSettings` module in Confluence

Following the deprecation notice, we have now made the route parameter mandatory for the confluence:spaceSettings module.

For detailed information on the available properties for confluence:spaceSettings, please refer to our documentation: https://developer.atlassian.com/platform/forge/manifest-reference/modules/confluence-space-settings/.

Added New batch of Jira Forge product events

We’re happy to introduce a new batch of Jira Forge product events for the following entities:

  • Project (deleted)

  • Issue (deleted)

  • Attachment (deleted)

  • Comment (deleted)

  • Worklog (deleted)

Follow the links to read more about them.

Added Forge support for IP allowlisting

Forge apps now support the IP allowlisting feature, which is available with Premium plans for Jira, Jira Service Management, and Confluence.

With this update, Forge apps installed on sites with IP allowlisting enabled can now make Jira API requests and Confluence API requests by default. This means customers no longer need to manually add https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#Outgoing-Connections to their allowlist.

20 June 2024

Added Increase in the limit of app installations when viewing logs

Previously, you could only view logs for a maximum of 400 app installations. We’ve now increased this from 400 to 3500 app installations.

This upgrade is only available for the new experience of viewing app logs. The previous experience still has the maximum limit of 400 app installations.

Added Export functionality added for Forge Macros built with UI Kit 2 and Custom UI

Functionality to export Forge Macros built with UI Kit 2 and Custom UI has been added via the adfExport property of the macro module. See the macro module documentation and associated tutorial for instructions on how to utilize the new property.

Rate this page: