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.

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).

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.

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.

Following a recent incident (see details), we have temporarily paused automatic Connect to Forge migrations. Our team is actively working to enhance system robustness and prevent similar issues from occurring in the future.

Once these improvements are complete, we will re-enable and resume the migration process.

Following our prior deprecation notice, you can no longer publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace.

From now on, all Atlassian Marketplace apps should be built using Atlassian’s Forge platform.

Forge platform will be undergoing maintenance:

• in FedRAMP production on September 21, 2025 between 5-6am UTC

• in commercial production on September 28, 2025 between 5-6am 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.

The allow-popups attribute of the sandbox directive (content security policy) is now supported in Forge Custom UI and UI Kit apps when using * as your client egress configuration. This enables external content (such as those from 3rd party integrations) to open properly in new tabs instead of being blocked by browser security restrictions.

With this enhancement, external content will open in a new browser tab while keeping your Forge app running.

For more information, see the valid domain formats documentation.

We're releasing a set of space role APIs for Confluence instances that have opted into Role Based Access Control (RBAC). These APIs will allow you to create, update, and delete custom space roles. Custom space roles let you tailor access beyond Confluence's default space roles, making it easy to match internal workflows and ensure the right people have the right access.

Macro Autoconvert has be updated to allow custom URL schemes to be used as matchers for URLs. See the Macro Autoconvert docs https://developer.atlassian.com/platform/forge/manifest-reference/modules/macro/#macro-autoconvert

We are announcing the deprecation of the following Connect Javascript API methods:

• getContentProperty

• setContentProperty

• syncPropertyFromServer

• Deprecation announcement: August 26, 2025

• Removal date: February 26, 2026

• These methods use the deprecated V1 REST APIs.

• On and after the removal date, all requests to the listed methods will result in a 404 Not Found response.

We recommend migrating to the V2 for these methods before the removal date.

• getContentPropertyV2

• syncPropertyFromServerV2

• postPropertyToServerV2

• updatePropertyToServerV2

Understand more about the usage of these methods.