Data limits and guardrails
To improve performance, reliability, and scalability in all Jira Cloud instances (including Atlassian Government Cloud), new limits and guardrails are being introduced for custom fields, work types, work items, and spaces. These changes help you manage data more effectively and prevent performance issues as your site grows.
This page explains what’s changing, why, and how you can stay within the new boundaries.
This page is for company-managed spaces
To check whether your space is team-managed or company-managed, select More actions (•••) next to the space name in either the header or the sidebar. At the bottom of the menu that opens, your space details will be shown.
More about the difference between company-managed and team-managed spaces.
Team-managed spaces have a current limit of 50 custom fields per space.
What’s changing
Guardrails are recommended data thresholds. If you exceed them, your site’s performance may be affected. These are best practices, not mandatory.
Limits are data thresholds that can’t be exceeded.
New limits starting February 2026
Starting in February 2026, the Jira Cloud family of apps will enforce new hard limits on certain data types to prevent performance issues as your site grows.
The limits are:
Fields: Maximum 700 fields per space
Calculated based on fields included in the field configuration schemes associated with the spaces
System fields won’t count towards the 700 field limit, but global custom fields will count unless their context is scoped specifically to certain spaces
No limit on the total number of custom fields across the site
Work types: Maximum 150 work types per space
Guardrails and best practices
We recommend following these guardrails for easier data management and configuration.
The guardrails are:
Work items: 18,000,000 work items per site
Spaces: 8,400 spaces per site
How to meet the limits
You must have the following to do the things described in this section.
Role: Site admin
The best way to reduce your footprint is to reuse existing global fields and delete outdated fields, work types, work items and spaces, helping to optimize your site for expansion and usability. Read about ways you can optimize your field configuration specifically
Start by understanding your site’s current usage.
The Field configuration schemes will show the number of fields included in your site. Unused fields are identified as those with no defined contexts, not appearing in any space, or not associated with screens in Jira. These evaluations may include updates by automation or third-party tools.
The Work type schemes will show the number of work types on your site.
Jira will let you know if you're approaching the limit, and offer ways to clean up unused data across spaces.
To view and manage your site’s usage:
From the global navigation, go to Settings (), then Work items.
From the sidebar, navigate to either Work type schemes or Field configuration schemes.
Review your fields or work types. Select Optimize scheme (even if you’re under the limit).
To remove unused fields or work types, select Review actions in the first section. Consider cleaning up your default field configuration by removing obsolete or rarely used fields.
To create a new scheme with only current and used fields or work types, select a space in Create a scheme variant, then Review actions.
Select Redefine configuration scheme to group spaces that use similar fields or work types and create a new scheme.
Starting in February 2026, if your space exceeds the 700 field or 150 work type limit, you’ll be prevented from associating additional fields or work types to your space until you reduce your data.
Existing configurations exceeding these limits will remain functional, and no existing data will be deleted. Exceeding limits does not directly degrade performance, but it may make management and troubleshooting more complex.
Optimize your spaces on Enterprise and Premium plans
The site optimizer can help you scope global custom fields to specific projects, identify unused fields, and create targeted field configurations. Read more about the site optimizer
Using a Standard plan?
Standard plan users can manage fields by reviewing field usage details in their field configuration schemes and using REST APIs or custom scripts for more detailed audits.
Was this helpful?