Jira Cloud limits: all 10 configuration limits and 4 guardrails
30-day free trial. Standard is free for up to 10 users. Runs on Atlassian, zero egress.

- 69 / 700 fields per space
- 6 / 150 work types per space
In this guide
Jira Cloud enforces 10 configuration limits, on fields, work types, options, security levels, permission grants, releases, workflows, statuses, components and priorities, and publishes 4 guardrails for the site. This page lists each value, its scope, its enforcement status and how it is counted, with a link to Atlassian's documentation for every row.
The values come from Atlassian's page on data limits and guardrails, checked on 18 October 2026. They are the same for every Jira Cloud plan. LimitRadar, the Jira Cloud limits app from Radrly, ships the same catalog inside the app.
The 10 limits
Two limits have been enforced since March 2026. The other eight are switched on progressively from September 2026, on a date that varies per site, and Jira does not report whether a progressive limit is already active on yours.
| Limit | Value | Enforcement | How it is counted |
|---|---|---|---|
| L1. Fields per space | 700 | Enforced since 2026.03 | Measured per space. Fields in the field schemes associated with the space. Trashed fields do not count. One field can count in many spaces. LimitRadar also shows the count excluding locked fields until a native screen comparison confirms whether locked fields count toward 700. Atlassian source |
| L2. Work types per space | 150 | Enforced since 2026.03 | Measured per space. Work types in the work type schemes associated with the space. Team-managed spaces count the work types on that space. Atlassian source |
| L3. Options per field | 20,000 | Progressive rollout from 2026.09 | Measured per field. Options of a single field, across all contexts. Whether disabled options count is not confirmed by Atlassian. Atlassian source |
| L4. Work item security levels per space | 50 | Progressive rollout from 2026.09 | Measured per security scheme. Work item security levels in one security scheme. The same usage is shown on every space that uses the scheme. There is no granular scope to delete levels, so cleanup is guidance and a link to the native tool. Atlassian source |
| L5. Grants per permission | 50 | Progressive rollout from 2026.09 | Measured per permission scheme. Grants of one permission inside a permission scheme. Atlassian source |
| L6. Releases per space | 15,000 | Progressive rollout from 2026.09 | Measured per space. Unreleased and released versions on the space. Archived releases are not intended to count, so LimitRadar shows both numbers. Atlassian source |
| L7. Workflows per workflow scheme | 150 | Progressive rollout from 2026.09 | Measured per workflow scheme. Distinct workflows mapped in one workflow scheme, including the default workflow. Atlassian source |
| L8. Statuses per workflow | 200 | Progressive rollout from 2026.09 | Measured per workflow. Statuses in one workflow. Atlassian source |
| L9. Jira components per space | 10,000 | Progressive rollout from 2026.09 | Measured per space. Jira components on the space. Compass components are not included. Atlassian source |
| L10. Priorities per space | 100 | Progressive rollout from 2026.09 | Measured per priority scheme. Priorities in the priority scheme assigned to the space. The applicable configuration is mapped to that scheme. Atlassian source |
The 4 guardrails
Guardrails are recommendations, not enforced limits. Jira does not block a change when a site goes above one.
| Guardrail | Value | How it is counted |
|---|---|---|
| Work items per site | 30,000,000 | Approximate work item count for the site. This is a recommendation, not an enforced limit. Atlassian source |
| Spaces per site | 30,000 | Spaces returned by project search. This is a recommendation, not an enforced limit. Atlassian source |
| Space role actors per space | 5,000 | Role actors on one space. LimitRadar shows the count with and without JSM customer accounts, because native warnings have counted them. Atlassian source |
| Space roles per user per site | 2,000 | Highest number of roles one account holds inside a single space. This is a lower bound for the site total. Account ids are not stored and there is no per-user list. Atlassian source |
What happens when you exceed a limit
Jira does not delete or change configuration that is already above a limit, and people keep creating and updating work items. What stops is growth: an admin cannot add another entity of that kind to the scope until usage comes down. A bulk action that would take a scope over the limit is rejected in full, with nothing partly applied, so a bulk add of 30 fields to a space at 690 fails as a whole rather than adding 10.
If you migrated from Server or Data Center and landed at 90% or more of a limit, Jira applies a three-month temporary exemption for that entity. Put its end date in your calendar.
How to check natively
On Premium and Enterprise, the site optimizer in Settings > System shows the spaces approaching or over the fields per space limit; see Optimize fields per space. On other plans, Atlassian points to the usage details in Jira settings plus REST APIs or custom scripts. For most of the other limits that means opening each scheme, workflow or field and counting.
How to check in LimitRadar
LimitRadar counts all 10 limits and the 4 guardrails for every scope with each daily snapshot, on every Jira Cloud plan.
- Overview shows each limit with its highest scope, a colour band and the enforcement status as Atlassian publishes it.
- Limits lists every scope for one limit, sorted by usage, with the forecast. See Limits and counting rules.
- Guardrails shows the 4 site guardrails with the counting rule. See Guardrails.
- Next to block ranks the scopes expected to reach a limit soonest, and What if I add tells you whether Jira would accept a planned bulk add or reject the whole action. See Next to block and forecast.
A limit LimitRadar could not read is marked as not available or not counted; it never shows an invented zero. For a step by step on the most common limit, read 700 fields per space in Jira Cloud. New to the app? Start with What is LimitRadar?
Quick answers
How many configuration limits does Jira Cloud enforce?
Atlassian publishes 10 enforced configuration limits and 4 guardrails. Fields per space and work types per space have been enforced since March 2026; the other eight are rolling out progressively from September 2026.
What happens when a bulk action would exceed a Jira Cloud limit?
It is rejected in full, with nothing partly applied. Configuration that is already above a limit keeps working, but Jira refuses to add more until usage comes down.
Are guardrails enforced like limits?
No. Guardrails are recommendations published by Atlassian. Jira does not block changes when a site goes above a guardrail.