Changelog

A new RFC is ready for review at : https://community.developer.atlassian.com/t/rfc-115-redesign-of-developer-space-for-forge-billing-roles-permissions-and-design-flows/96104/1

Forge Automation Actions is now available in Preview. This feature allows you to extend the Automation Platform and add new Forge-based actions to your app. During Preview, the Automation Actions in your app can be used in production environments.

For more information, see the Forge Automation Action documentation and share your feedback to help us improve

We've added new Confluence Forge events for user groups:

• avi:confluence:created:group – Triggered when a new user group is created in Confluence

• avi:confluence:deleted:group – Triggered when a user group is deleted from Confluence

These events let your Forge app automatically respond to group management changes, such as:

• Sending notifications when new groups are created

• Cleaning up group-related data when groups are deleted

The event payload includes group details like id and name.

For more details on the payload structure and required OAuth scopes, see the Confluence events reference documentation.

A new RFC is ready for review at : https://community.developer.atlassian.com/t/rfc-114-forge-extensibility-for-teams-app/95948

The waitlist is now open for the Forge Containers Early Access Program, launching in February 2026.

Forge Containers will allow you to run containerised workloads as part of your Forge app, giving you more flexibility over your runtime environment. You’ll be able to run custom binaries, use non-Node.js languages and execute long-running batch operations.

To participate, join the waitlist to express your interest and help us plan cluster capacity for the program:

https://go.atlassian.com/forge-containers-eap-waitlist

We’ve added new Confluence Forge events for users:

• avi:confluence:created:user

• avi:confluence:deleted:user

You can use these events to invoke your Forge app function when a user is added to or deleted from Confluence. For more details see the Confluence events reference documentation.

We have introduced new Confluence display conditions for Forge in Preview:

• entityPropertyContainsAnyUserGroup

• hasPagePermission

• hasSpacePermission

• userIsExternalCollaborator

Additionally, entity property conditions in Confluence now support app and user properties.

Learn more about these conditions here.

Forge platform will be undergoing maintenance in commercial production on October 12, 2025 for approximately 1 minute between 3-4am UTC

During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

You can now set the rendered viewport height of a macro with setMacroViewportHeight, which is an asynchronous function that can be used in edit mode. The function takes a string height parameter and returns true if the update to the ADF succeeded, and false if it failed. This function works only in edit modes (for example a live doc, or edit mode of a Confluence page).

The Forge Object Storage package now features two new methods for managing pre-signed URLs for an object:

• createUploadUrl: creates a pre-signed upload URL for an object using its properties as parameters.

• createDownloadUrl: creates a pre-signed download URL for an object using its objectId.

See Storing, downloading, and deleting large objects for more information.

Starting Mar 31, 2026, the ability to update existing Jira or Confluence apps using a Connect descriptor on the Atlassian Marketplace will be deprecated. This change aligns with our strategic shift to the Forge platform.

Additionally, this means the following:

1. Atlassian Marketplace will no longer poll for Connect descriptor updates. However, apps using Connect modules that have adopted the Forge manifest can still receive updates.

2. Installing new Connect private apps via Connected Apps will no longer be available and private app development should move to Forge.

What this means for partners:

1. Partners should plan to update Connect apps on the Atlassian Marketplace by Mar 30, 2026 at the latest.

2. All new app development should be conducted on Forge.

You can now add and edit configuration for function validators in the new workflow editor. This update lets you save configuration data and pass it to the lambda function under the configuration parameter during invocation. This makes it easier to customize and manage workflow validation logic.

For more information, see Jira Workflow Validator.

We're introducing new App Property API endpoints to retrieve Forge App Properties in Confluence & Jira, now available in Preview.

The APIs enable developers to

• GET all Forge app properties, or

• GET individual app properties by key

in both Jira and Confluence, enhancing the flexibility and functionality of Forge apps.

For further details on implementing this new feature, refer to the Jira App Property API Documentation & Confluence App Property API documentation.

We're updating the cursor behavior in the Storage Remote GraphQL API for both Key-Value Store (KVS) and Custom Entity stores. Currently, KVS returns individual cursors for every edge, while Custom Entity edge cursors always point to the last element of the current page. To reduce confusion and align with the new REST API, both stores will now return a single cursor at the end of each page.

This change will take effect after March 20, 2026.

We've updated our documentation to clarify the existing rate limits for network requests and web trigger operations in Forge. These limits have been in place to protect the reliability and stability of our platform, but are now described in more detail to help developers understand how they apply.