We are releasing a Workflow Preview API that offers read-only access to workflow configurations. This API supports the current workflow view for work items within a project context. The preview includes nearly all the content of the full workflow but limits exposure of rule configurations and status properties. It is also available to users with View (read-only) workflow permissions.

To support Jira performance at scale, we are introducing a limit on how many work types and how many fields can be associated to a company-managed project in Jira cloud:

• The admin user interface and related APIs will restrict the association of more than 150 work types to a single work type scheme.

• Similarly, they will also limit the association of more than 700 fields within the single field configuration scheme.

The limit will be effective starting Feb 9, 2026.

Exemption which will be allowed to go over these limits. Examples include:

• Installing a new app

• Enabling a new product

• Upgrading (or downgrading) a license tier

• Creating a new project

• Migrations

Jira Admins will have access to streamlining tools designed to eliminate unused fields and work types. This initiative aims to ensure that the field configuration scheme and work type scheme remain within the established limits.

Support documents

• This is building on top of what we announced in https://community.atlassian.com/forums/Jira-articles/Announcement-Changes-to-field-and-work-type-configuration-in/ba-p/3023478

• Fields https://support.atlassian.com/jira-cloud-administration/docs/optimize-fields-in-your-project/

• Work types https://support.atlassian.com/jira-cloud-administration/docs/optimize-work-types/

The following APIs will be impacted:

• Add work type to a work type scheme: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-type-schemes/#api-rest-api-3-issuetypescheme-issuetypeschemeid-issuetype-put will return HTTP 400 if the scheme is over a limit

• Create issue type scheme: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-type-schemes/#api-rest-api-3-issuetypescheme-post will return HTTP 400 if the issue type count is over a limit

• Assign work types to field configurations: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-field-configurations/#api-rest-api-3-fieldconfigurationscheme-id-mapping-put will return HTTP 400 if the scheme is over a limit

Atlassian is introducing burst API rate limiting for Jira Cloud to enhance reliability and performance. This industry standard approach helps prevent service disruptions by controlling excessive API requests from apps and scripts using API tokens, ensuring a smoother experience for all users.

On Jul 28, 2025, we announced the addition of number field formatting through the Atlassian GraphQL Gateway (AGG) for company-managed projects in Jira.

We’ll start progressively rolling out this change to each tenant today (Aug 27, 2025). We expect to finish this rollout on Sep 11, 2025.

Following our previous announcement, eligible apps migrating from Connect to Forge will now automatically roll out to customers. Rollouts will occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.

Apps which have previously adopted Forge from Connect and have not opted in to minor updates will be progressively migrated in the coming weeks.

See https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-forge-updates-preview/ for details about eligibility. To test and validate your app’s migration process, you can still opt-in to the staged migration process.

We're reminding developers that the "Myself-> Set locale" API was previously marked as deprecated. This API is being deprecated because user management is now handled through the Admin Hub, not within Jira.

This change will take effect on Feb 14, 2026.

Starting 24 November 2025, Jira will require the “Link Issues” permission for all linking operations on both outwards and inwards issues. Previously, the "Link Issues" permission was only required on the outward issue. This change addresses a long-standing discrepancy in the permission level required for inward and outward issues.

An error response will occur if the user does not have the required permission while creating or updating the issue in the UI, operations via REST APIs, or automation rules.

You may need to update your app as a result of this change. For more information, see the More details section below.

Note, there are no changes to the “Browse Project” (and Issue Level Security if configured) permission requirement on both issues.

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.