Atlassian doesn't set a hard cap on how many projects a Jira Cloud site can have. It lists 30,000 spaces per site as a guardrail, not an enforced limit. What it does enforce are limits inside each space, such as 700 fields and 150 work types per space, with eight more limits being rolled out progressively from September.
Projects are now called spaces
If you've searched for a Jira project limit and found nothing, part of the reason is the name. Atlassian's data limits page now says space where older Jira wording said project. The other reason is that there isn't a hard number for how many you can have.
Limits versus guardrails
Atlassian uses two different words, and they mean very different things. A limit is a maximum the software enforces. A guardrail is a recommended threshold that isn't enforced. The number of spaces sits in the second group.
| Guardrail (recommended, not enforced) | Value |
|---|---|
| Spaces per site | 30,000 |
| Work items per site | 30,000,000 |
| Space role actors per space | 5,000 |
| Space roles per user per site | 2,000 |
The limits Jira does enforce
| Item | Limit | Status |
|---|---|---|
| Fields per space | 700 | Enforced since March |
| Work types per space | 150 | Enforced since March |
| Releases per space | Fifteen thousand | Rolling out from September |
| Workflow statuses per workflow | 200 | Rolling out from September |
| Components per space | 10,000 | Rolling out from September |
| Work items shown on a board or backlog | 5,000 | Company-managed boards |
The September rollout covers eight limits in total. Alongside those in the table, it includes 20,000 field options per field, 50 security levels per space, 50 permission grants per permission, 150 workflows per workflow scheme and 100 priorities per space. Rollout timing varies from site to site.
On fields: there's no limit on the total number of custom fields across a site, and trashed fields don't count toward the 700-per-space limit. So clearing out old fields really does give you room.
What happens when you're over
Existing configuration that's already over a limit keeps working. But you'll need to bring it below the limit before you can add more of that thing. Administrators can't change limit values in Jira settings; they can only view usage and reduce it.
Boards behave a little differently. A board or backlog that goes past 5,000 work items shows the first 5,000, with a warning to admins to edit the board filter. If a board suddenly looks incomplete, a filter that's too broad is the likely cause.
For teams moving from Server or Data Center, Jira applies a three-month temporary exemption for any entity where usage is at or above 90% of a limit, which gives you time to tidy up after migrating.
Why there's no single number to find
Atlassian Support's page makes the point that explains every confusing search result. Jira caps what's inside a space, such as fields, work types and soon eight more things, rather than the number of spaces. The 30,000 number is a guardrail, not a block. For most small and mid-sized businesses, the limits you'll feel first are fields per space and items on a board.
Tools for keeping within limits
Enterprise and Premium plans include a site optimiser. On Standard, you manage limits with usage details, REST APIs or scripts. Either way, a quarterly tidy of unused fields and work types keeps you well clear.
How Azure DevOps and Trello set limits
Microsoft lists limits of 5,000 teams per project and 1,500 delivery plans per project for Azure DevOps, and says each backlog can display up to 10,000 work items.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Trello's developer docs show an example board limit of 5,000 open cards and say actual limits vary by board and account. If you're comparing tools, see my roundups of Jira alternatives and project management software.
My advice for Jira admins
Stop worrying about the number of spaces and watch what's inside them. Keep fields per space well under 700, keep board filters tight so nothing hits 5,000, and check the new limits as they reach your site. If you're migrating, use the three-month exemption to clean up rather than to delay.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What's the maximum number of projects in Jira Cloud?
Atlassian lists 30,000 spaces per site as a recommended guardrail rather than an enforced limit.
What are the enforced Jira limits?
700 fields and 150 work types per space, enforced since March.
What's changing next?
Eight more limits are rolling out progressively from September, including fifteen thousand releases per space and 200 workflow statuses per workflow.
Can I raise a limit?
No. Administrators can't change limit values, only reduce usage.
How many work items does a board show?
The first 5,000 when a board or backlog exceeds that limit.


