Atlassian developer changelog

As of Oct 9, 2025, we’ll be moving the location of the configuration for JSM approvals in company-managed projects from status properties to a new approvalConfiguration property on the status. The following endpoints will be affected:

• Bulk get workflows

• Bulk create workflows

• Validate create workflows

• Bulk update workflows

• Validate update workflows

Refer to CHANGE-1656 for more details.

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

What’s new in Confluence 10.1?

• Find and sort most used macros in your site

• Manage your integrations and automations with service accounts

• Connect securely with OAuth 2.0 for app links

• Upgrade to React 18.3 and latest Atlaskit

• Editor upgrade to TinyMCE 7.9.1

• Lots more!

To learn more, see Confluence 10.1 release notes.

Download the latest version

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.

To help Marketplace partners distinguish between Commercial and AGC-compatible (Atlassian Government Cloud) apps, we have introduced a new API field: cloudComplianceBoundaries across Marketplace APIs.

The valid values for the API field are as follows:

• commercial: The standard commercial version of the app.

• fedramp_moderate: The AGC-compatible version of the app.

The new field is available in the following Marketplace APIs:

• Apps -> https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-group-apps

• App versions -> https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-app-versions/#api-group-app-versions

• Reporting → The new field will be added to license and transaction reports to help partners differentiate AGC licenses and transactions from Commercial Cloud licenses and transactions.
  https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-group-reporting

  • Licenses

  • Export Licenses

  • Initiate Async Export licenses

  • Transactions

  • Export transactions

  • Initiate Aysnc Export Transactions

• Partners are requested to review the latest API documentation for more details.

• Note: AGC-compatible apps are not yet enabled for general availability (GA) to customers and therefore, Partners will not see any AGC licenses or transactions at this time.

More details on GA date for customers will be shared via QRG separately. For any questions, please raise an ECO-HELP ticket.

We’re pleased to announce that Crowd 7.1.0 is now available. We have made some security enhancements and some changes to the supported platform. Explore Crowd 7.1.0 to see the full list of updates.

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.

We are excited to announce the release of a comprehensive new guide for Marketplace Partners on how to publish and market apps for Atlassian Government Cloud (AGC). This introduces a step-by-step process for listing AGC-compatible apps,
https://developer.atlassian.com/platform/marketplace/publish-and-list-agc-apps/

Key Updates:

1. New Documentation Available

   1. Required steps to publish AGC-Compatible app

   2. How to create and submit an AGC app version via the Marketplace Partner Portal

   3. Guidance on updating AGC-specific app details and leveraging content from your commercial cloud version

2. Pricing and Licensing for AGC Apps

   • Partners can set and upload pricing specifically for AGC-Compatible app

3. Support and Resources

   • Additional resources:

     • https://developer.atlassian.com/platform/framework/agc/guides/build-agc-compatible-forge-apps/

     • https://developer.atlassian.com/platform/framework/agc/

Action Required:

• Review the new guide and update your app listings and processes as needed. Please raise an ECO-HELP ticket in case you have any queries.

• Marketplace Reporting: We will share how to identify Atlassian Government Cloud licenses and transactions via Changelog on Friday, 3rd October.

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

As Jira instances grow in size and scale, the default search engine, Lucene, may be slower to index and return search results. To address this, Jira Data Center now offers an alternative search engine as an opt-in feature — OpenSearch

The second early access program (EAP) of OpenSearch for Jira gives you an opportunity to test apps' compatibility with OpenSearch. More about OpenSearch for Jira EAP02

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.

A Confluence 10.1 beta version is available now for testing. To find out what’s changed, check out Confluence 10.1 beta release notes.

Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.

Download the latest beta

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.