Updating workflows via the Bulk update workflows API will discard existing draft workflows that are associated with the workflow.

This change is being made because draft support will be discontinued with the retirement of the old workflow editor.

As of Jul 7, 2025 , the following APIs will stop returning usage data in their responses:

Workflows

• Bulk get workflows

• Bulk create workflows

• Bulk update workflows

Statuses:

• Bulk get statuses

• Search statuses paginated

• Bulk create status

Workflow schemes:

• Bulk get workflow schemes

Refer to CHANGE-2298 for more details.

As part of the Atlassian visual refresh updates, we updated the UI Kit Icon component. Some glyphs get a new look, and many more glyphs have been added. There are also a number of deprecations, as detailed below.

On Jun 24, 2025, we announced the addition of number field formatting through the Atlassian GraphQL Gateway (AGG) for Jira team-managed projects.

In October 2024, we announced the deprecation of Deprecation of some JQL search and evaluate expression endpoints. These deprecated search endpoints are now being removed:

• GET /rest/api/2|3|latest/search

• POST /rest/api/2|3|latest/search

• POST /rest/api/2|3|latest/search/id

• POST /rest/api/2|3|latest/expression/eval

For full details of this deprecation, including replacement endpoints, see https://developer.atlassian.com/changelog/#CHANGE-2046.

Forge Remotes are now available in the Atlassian Government Cloud. Please refer to the AGC documentation for details on supporting Forge Remotes within your AGC Forge app.

We are deprecating the following Atlassian Connect-related unscoped npm packages in favor of their @atlassian scoped equivalents.

Starting 24th of July 2025, these packages will no longer be supported, and we recommend transitioning to the corresponding scoped packages instead.

The affected packages are:

The scoped packages maintain 100% API compatibility with their unscoped versions, ensuring a seamless migration experience. We recommend updating to the scoped versions as soon as possible before the deprecation date.

All of these packages are part of the Atlassian Connect ecosystem and are used for developing Connect apps. The scoped packages provide identical functionality but align with our standardized package naming conventions. This change helps ensure consistency across our npm ecosystem and improves package security.

To update your dependencies, replace the unscoped package names with their scoped equivalents in your package.json files.

If you encounter any issues during migration, please reach out through the Developer Community forums.

We are augmenting the existing team-managed project 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 retrieve, and display monetary values with correct formatting and units through the Atlassian GraphQL Gateway (AGG) by:

• Querying formatUnit, formatStyle, and formatDecimals on JiraNumberFields

• 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 capability will be extended to number fields in company-managed projects in the coming months and communicated separately

We’re introducing the ability for apps to publish events, allowing for enhanced interoperability between apps. This feature enables apps to subscribe to events using the existing https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/ module, opening up new possibilities for app interactions.

A new getUrl method has been added to router in @forge/bridge. The method will accept a NavigationLocation object and return a URL object for the corresponding destination.

This method is in Preview. For more details, see the router documentation.

We have enhanced Bulk Move API to allow users to move both parent and child work items/issues in a single request, as well as move multiple work items/issues of different types in the same request.

REMINDER As previously announced in CHANGE-2298, starting from Jul 7, 2025, we will begin the process of deprecating the expands query parameter used for retrieving associated projects, workflows, issue types, and schemes across various Jira Cloud APIs. We strongly recommend transitioning to the usage APIs detailed here.

Affected APIs and parameters

Workflows:

• Bulk get workflows: The ability to use the workflows.usages and statuses.usages expands will be deprecated.

• Bulk create workflows: Usage information will no longer be included in responses.

• Bulk update workflows: Usage information will no longer be included in responses.

Statuses:

• Bulk get statuses: The usages and workflowUsages expands will be deprecated.

• Search statuses paginated: The usages and workflowUsages expands will be deprecated.

• Bulk create status: The usage and workflowUsages fields will no longer be returned.

Workflow schemes:

• Bulk get workflow schemes: The workflows.usages parameter will be deprecated.

You may need to update your app as a result of this change - see the More details section.

We have published a new migration guide to assist you in transitioning your Forge custom fields to use the isInline property.

The guide includes two practical examples:

• Migrating a Forge custom field to render inline

• Migrating a Forge custom field to render in a modal

For more details, please refer to https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#inline-edit-migration-guide

The list of modified fields in the Jira workflow validator has been expanded to include two new fields:

• Linked Issues

• Comment

For a complete list of all supported field types, please refer to the documentation: Jira Workflow Validator.

We are announcing support for the following Connect on Forge Jira Software provider modules:

• jira:jiraDevelopmentTool

• jira:jiraFeatureFlagInfoProvider

• jira:jiraDeploymentInfoProvider

• jira:jiraBuildInfoProvider

• jira:jiraRemoteLinkInfoProvider

• jira:jiraSecurityInfoProvider

• jira:jiraOperationsInfoProvider

• jira:jiraDevOpsComponentProvider