Atlassian developer changelog

The Teamwork Graph Smart Links module is now available in Forge, allowing developers to create custom Smart Links that enhance URLs with additional metadata, thumbnails, and status indicators.

This feature enables rich link previews and improves user experience by providing contextual information and actions for linked content from supported platforms.

For more information, see Smart Link module documentation and Teamwork Graph supported object type documentation.

The Smart Links module is currently only available for apps installed into Jira.

We’re happy to present the sixth and final 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-m0015.

We are extending the deprecation period of the Convert content body v1 REST API in Confluence Cloud to Feb 1, 2026.

As mentioned in the original deprecation announcement, developers will be able to use the Asynchronously convert content body endpoint as an alternative. We will make sure that known load and timeout complexities with the asynchronous endpoint are resolved by the time the Convert content body v1 REST API is deprecated.

We've updated the Forge module jira:projectPage to include board.id and board.type in its extension data. This change allows developers to access board-specific information directly within the project page, enabling more tailored and context-aware apps.

We are augmenting the existing company-managed Number custom field in Jira Cloud to support unit configuration. This will include currency and percentage unit types, as well as formatting.
Apps will be able to do the following through the Atlassian GraphQL Gateway (AGG):

• Retrieve and display values with correct formatting (currency, percentage, or number) by querying formatUnit, formatStyle, and formatDecimals on JiraNumberFields

• Set and update the number field formatting via setting formatConfig when creating or updating custom fields

Please note that:

• The underlying Number value storage will remain unchanged, meaning that this is a purely additive change and no action is needed.

• JQL search will behave exactly like the number field works today. It will be unaware of the currency unit through all the access points.

• This functionality has already been released in team-managed projects. See the announcement here

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.