Data limits and guardrails in Jira Cloud
Data limits and guardrails help maintain the performance, reliability, and scalability of Jira Cloud as your site grows.
This page explains the limits Jira currently enforces and the additional limits Jira will begin enforcing in September 2026. It also explains recommended guardrails for large Jira sites, what will happen when a limit is reached, and where administrators can view and manage the affected configuration.
Limits apply to the Jira Cloud family of apps, including Jira, Jira Service Management, and Jira Product Discovery, where the relevant feature is available.
はじめる前に
Most configuration covered on this page can be viewed and managed by a Jira administrator.
Some space-level configuration, such as releases and components, can also be managed by someone with the appropriate space administration permission.
The limit values are defined by Atlassian. Administrators can view and reduce their usage, but they can’t change the limit values in Jira settings.
Understand limits and guardrails
A limit is a software-enforced maximum for a specific type of data or configuration.
When enforcement is active and a field, permission, space, scheme, or workflow reaches its limit, Jira prevents an administrator from adding more of that entity within the affected scope.
Existing configuration can remain above the limit and will continue to work, but it must be reduced below the limit before more of that entity can be added.
A guardrail is a recommended threshold intended to help administrators maintain a manageable data shape.
Guardrails aren’t enforced limits. Exceeding a guardrail won’t automatically block an action, but it may increase configuration complexity or affect performance, depending on factors such as query scope, traffic patterns, apps, and integrations.
Limits currently enforced
Jira began enforcing the following limits in March 2026.
Fields - 700 per space (fields included in field configuration schemes associated with the space)
Work types - 150 per space (work types included in work type schemes associated with the space)
For the field limit:
Trashed fields don’t count toward the 700-field limit.
There is no limit on the total number of custom fields that can exist across the site.
A field can count toward more than one space if it is included in schemes associated with those spaces.
If a space reaches either limit, Jira prevents an administrator from associating additional fields or work types with that space until usage is reduced. Read about ways you can optimize your field configuration specifically
Existing configuration remains functional, and Jira doesn’t automatically delete existing data.
Additional limits starting September 2026
From September 2026, Jira will progressively begin enforcing eight additional configuration limits.
Because this is a progressive rollout, the exact date on which enforcement becomes active for an individual entity or site may vary.
Field options per field - 20,000
Work item security levels per space - 50
Permission grants per permission - 50
Releases per space - 15,000
Workflows per workflow scheme - 150
Workflow statuses per workflow - 200
Jira components per space - 10,000
Priorities per space - 100
フィールド オプション
The limit applies to the options associated with an individual field. When a field reaches the limit, an administrator won’t be able to add another option to that field. Existing options will remain available.
Manage optimizing field options
Work item security levels
When the applicable configuration reaches the limit, an administrator won’t be able to add another security level for the affected space. Existing security levels and work items using those levels will continue to work.
Manage work item security levels
Permission grants
A grant assigns a permission to a user, group, space role, or another supported permission holder. When a permission reaches the limit, an administrator won’t be able to add another grant to that permission. Existing grants will remain active.
Bulk remove redundant space roles from permission schemes
リリース
Archived releases aren’t intended to count toward this limit.
When a space reaches the limit, an administrator won’t be able to create another release in that space. Existing releases and work items associated with them will remain available.
ワークフロー
When a workflow scheme reaches the limit, an administrator won’t be able to add another workflow to that scheme.
Workflows used by the scheme will continue to operate normally.
ワークフロー ステータス
When a workflow reaches the limit, an administrator won’t be able to add another status to that workflow.
Existing statuses and transitions will continue to work.
Delete a status in Jira Cloud Workflow
Jira components
When a space reaches the limit, an administrator won’t be able to create another Jira component in that space.
Existing Jira components and work items using them will remain available. This limit applies to Jira components. It doesn’t apply to Compass components.
優先度
When the applicable priority configuration reaches the limit, an administrator won’t be able to add another priority to the affected space.
Existing priorities and work items using them will remain available.
What will happen when a limit is reached?
Jira will validate an administrative action when it is submitted.
If the affected configuration is already at or above its limit, Jira will reject an action that would add more of that entity.
If a bulk action would take the configuration above its limit, Jira will reject the action instead of partially applying it.
When a limit is reached:
Existing configuration will remain available and normal end-user activity will continue..
Jira won’t automatically delete, archive, disable, or modify existing configuration.
Users will still be able to create and update work items.
Administrators will still be able to perform unrelated configuration changes.
Other fields, permissions, spaces, schemes, and workflows below their limits will remain unaffected.
Jira will display an in-product message explaining that the relevant limit has been reached.
Enterprise および Premium プランでスペースを最適化
The site optimizer can help you manage limits, identify unused entities, and optimise space configuration. Read more about the site optimizer
If you are using a Standard plan
Standard plan users can manage entity limits by reviewing usage details in Jira settings and using REST APIs or custom scripts for more detailed audits.
View and manage usage in Jira administration
Jira will surface limit information and warnings in the administration areas where the affected configuration is managed.
The exact controls visible to you depend on your permissions, Jira product, edition, space type, and rollout status.
フィールド
Go to Settings, Work items, then Field configuration schemes.
Review the scheme and the spaces associated with it.
作業タイプ
Go to Settings, Work items, then Work type schemes.
Review the work types and associated spaces.
フィールド オプション
Go to Settings, Work items, then Fields.
For the field, select More actions, then Contexts and default value.
Then select Edit options for the relevant context.
Work item security levels
Go to Settings, then Work items, then Work item security schemes.
Open the scheme and select Security levels and edit.
Permission grants
Go to Settings, then Work items, then Permission schemes, then Remove.
Open the relevant scheme and review the grants under each permission.
リリース
Open the affected space and go to Releases.
Depending on the space type, release configuration may also appear under Space settings → Versions → More actions (⋯) → Delete.
ワークフロー
Go to Settings, then Work items, then Workflow schemes, then Edit/Delete.
Open or edit the relevant workflow scheme.
ワークフロー ステータス
Go to Settings, then Work items, then Workflows, then Edit, then Delete status.
Open the relevant workflow in the workflow editor.
Jira components
Open the affected space.
Go to Space settings, then Components then More actions (⋯) then Delete.
優先度
Go to Settings, then Work items, then Priorities and Priority schemes, then More actions (⋯) → Delete.
Review the priorities associated with the affected space.
Space role
Go to Settings, then System, then Space roles, then select View usage for a role.
To review membership for a particular space, open that space’s people or access settings.
Guardrails and recommended data shape
The following values are guardrails, not hard limits:
Work items per site - 30,000,000
Spaces per site - 30,000
Space role actors per space - 5,000
Space roles per user per site - 2,000
Performance at scale can also depend on:
The scope and complexity of JQL queries
Board and backlog configuration
Custom-field usage
Traffic and request patterns
自動化
Marketplace およびカスタム アプリ
連携
How to get help
If the introduction of these data limits and guardrails impacts your day‑to‑day usage, Atlassian Support is available to help you review and optimize your configuration. For assistance, please visit our Support site and create a ticket: Studio support
When contacting Support, include:
Your Jira site URL
The affected entity
The affected space, field, permission, scheme, or workflow
The current usage displayed in Jira
The action you are trying to complete
A screenshot of the warning or error
この内容はお役に立ちましたか?