Atlassian developer changelog

You can now name transitions that allow issues to move into a status from anywhere in the workflow.

1. Create Transition Modal:

   • Enable users to name ‘from any status’ transitions during creation.

2. Transition Side Panel:

   • Allow users to update ‘from any status’ transition names.

3. Status Side Panel:

   • Display the transition name.

4. Edit Status Modal:

   • Provide an option for users to retain the existing transition name or update it to match the new status name.

   • Add a transition preview card for this type of transition.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-101-forge-billing-developer-space-roles-and-permissions/94049

On Jul 27, 2025 from 10:00-13:20 UTC, we will be migrating our Custom Entity Store metadata to a new data source. During this time, the following commands will fail for any apps that have storage:entities declared in their manifest:

• forge deploy

• forge storage entities indexes list

KVS and Custom Entity Store operations will continue to work as normal.

Currently, global admins have access to both the new and old workflow editors for CMP workflows. When a workflow is edited in Jira it opens in the admin’s default workflow editor. This may be the new or old editor based on user preference or system logic.

The default workflow editor API can be used to determine the default workflow editor for the authenticated user.

We are announcing support for the following Forge Jira Software provider modules. More information can be found in our documentation: https://developer.atlassian.com/platform/forge/manifest-reference/modules/index-jsw/

• devops:developmentInfoProvider

• devops:featureFlagInfoProvider

• devops:deploymentInfoProvider

• devops:buildInfoProvider

• devops:remoteLinkInfoProvider

For years, we’ve used Glitch to showcase our Trello developer example apps and Power-Ups. Unfortunately, Glitch has announced they are shutting down their app hosting service.

Because these example projects serve as invaluable documentation for our developer community, we’ve copied them over a public Bitbucket repository so they can continue to be referenced.

Check it out here! https://bitbucket.org/atlassianlabs/trello-glitch-example-projects/src/main/ . Be sure to read the README of that repository.

We’ve also updated our developer documentation to link to the public repository instead of Glitch.

Forge CLI version 12.2.0 is now available. We have updated the deprecated dependencies so that when you install this version of the CLI, you won’t see any deprecation warnings.

For more information on installing and upgrading the Forge CLI, visit our reference page.

We will be removing the ability to use two unlisted board endpoints on Jul 22, 2025:

• /rest/greenhopper/1.0/xboard/work/allData

• /rest/greenhopper/1.0/xboard/work

As an alternative, consider the following public API options:

• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-issue-get for board issues

• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-sprint-get for board sprints

• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-group-board for an extensive list of public board endpoints

Effective 18 Aug 2025, the following fields in the Bitbucket Cloud REST API will be updated to support larger values:

• Pull request comment ID: Will change from int32 to int64

• Pull request task ID: Will change from int32 to int64

This change may affect API clients and webhook consumers that explicitly handle these fields as 32-bit integers. Please update your integrations to handle 64-bit integer values for these fields.

The following UI Kit components are now generally available:

• https://developer.atlassian.com/platform/forge/ui-kit/components/adf-renderer/

• https://developer.atlassian.com/platform/forge/ui-kit/components/calendar/

• https://developer.atlassian.com/platform/forge/ui-kit/components/checkbox-group/

• https://developer.atlassian.com/platform/forge/ui-kit/components/empty-state/

• https://developer.atlassian.com/platform/forge/ui-kit/components/inline-edit/

• https://developer.atlassian.com/platform/forge/ui-kit/components/list/

• https://developer.atlassian.com/platform/forge/ui-kit/components/popup/

• https://developer.atlassian.com/platform/forge/ui-kit/components/time-picker/

No code changes are required. These components will now follow the 6 month deprecation period if any breaking changes were to be made.

We're introducing a new App Property API for Forge apps in Confluence, now available in Preview.

This API enables developers to PUT and DELETE app properties in Confluence, enhancing the flexibility and functionality of Forge apps. Retrieval of app properties will be made available through, Display Conditions for Confluence, which is coming soon.

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

We’re happy to present the third Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.

You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0012.

Crowd 7.0 EAP03 milestone is available now for testing.

To find out what else changed, check out Preparing for Crowd 7.0 or download the latest EAP

When an app moves from Connect to Forge today, developers can opt-in to automatically roll out the Forge version to existing Connect customers. Following the introduction of Forge bulk-upgrades, from Aug 18, 2025 the first update from Connect to Forge will now automatically rollout to customers when an app is eligible. Rollouts will now also occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.

Apps which have already moved from Connect to Forge and have not opted in for this behaviour will see customers progressively updated if their latest Forge version is eligible from Aug 18, 2025.

A Confluence 10.0 beta 3 version is available now for testing. To find out what’s changed, check out Confluence 10.0 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