Atlassian developer changelog

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.

We are adding two new Mandatory Privacy & Security tab questions.

1. “App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret”
   This question requires you to specify whether or not your app currently utilizes PATs (Personal Access Token) or another shared secret to function. More about PAT sharing policy. This ensures the response is being disclosed to customers for the small number of partner apps that still utilize PATs.

2. “Provide a reason/justification for the permissions that are required by your app.”
   This question requires you to specify a justification for the scopes requested by your app. This enables customers to have a better understanding of the reasoning for your app scopes when viewing the Privacy & Security tab details.
   :info: Note: The Permissions Justification field appears only if your app has at least one requested scope.

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 happy to present the release of Jira Software and Jira Service Management 11.1. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.1 release notes and Jira Service Management 11.1 release notes.

Download Jira Software 11.1 and Jira Service Management 11.1.

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.

We are introducing Entitlement Numbers to Data Center (DC) licenses, aligning them with Cloud Entitlements as previously announced (https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2798). To implement this, our internal data pipelines will be updated, specifically the appEntitlementId and appEntitlementNumber fields.

A 24-hour maintenance window is required to ensure 100% accuracy of data field updates to current paid Data Center licenses.
Maintenance window: 1:30am UTC, 25 September 2025 – 1:30am UTC, 26 September 2025.

During this period:

• Marketplace Reports will not reflect updates to current DC licenses, transactions or new Data Center licenses.

• Customers will be able to create transactions, create new licenses.

After the update, Marketplace reports will be backfilled on 26 September 2025 to accurately display DC license and transactions data.

Why this matters:

• This change lays the groundwork for future migration of Data Center licenses to the new billing system and Marketplace needs to ensure accurate Entitlement data is updated for Marketplace customers & Partners.

• Note: Licenses are not being migrated to the new billing system at this stage.

For detailed explanation of the changes, partners are requested to check our previous communication: https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2798 .
For questions or further details, please contact us via ECO-HELP tickets.