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

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

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 launching a Forge module to allow extension of the new home dashboards that are currently in open beta. This early access program (EAP) will enable partners to test the new module, and provide feedback and requests.

We plan to run this EAP for roughly 3 months and we are particularly keen to hear what is missing from the module and the additional areas of extensibility we can provide.

As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” (set forth in section 10 of the Atlassian Developer Terms) and are unsupported, subject to change without notice, and are not recommended for use in production environments.

To participate, please sign up for the EAP here.

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.