Atlassian enforces hard limits on Jira Cloud configuration. Enter your counts below to see what is already over. Everything runs in your browser — nothing is sent anywhere.
Enter your numbers to see where you stand.
These cannot be exceeded. Once you hit one, you cannot create new objects of that type in that container.
| What | Limit | Yours | Status |
|---|
The limits are per container, not per site. This is the part most people get wrong. Workflows are capped per workflow scheme — 400 workflows across your instance is fine, 151 inside one scheme is not. Statuses are capped per workflow, so your global status list can be far longer than 200.
So the number that matters is not your site total. It is your worst container. Check the biggest space, the biggest workflow scheme and the longest workflow first.
Atlassian uses two different words and they mean different things. Guardrails are recommended thresholds — cross them and performance degrades, but nothing blocks. Limits are hard: you cannot go past them. This page covers the hard limits, because those are the ones that stop work.
March 2026 — already in force. Fields and work types per space.
September 2026. Workflows per scheme, statuses per workflow, priorities and components per space, field options per field, plus limits on releases, permission grants and work item security levels.
Always confirm current values against Atlassian's data limits and guardrails documentation — Atlassian revises them.