Hello Atlassian Community!
Earlier this year, we shared our roadmap for growing our investment in a faster, cleaner Jira, introducing additional limits, guardrails, and data management tools to help your sites scale smoothly. Expanding on the field and work type limits introduced in February 2026, the eight new configuration limits announced in March 2026 are now live across Jira Cloud.
Here’s a quick recap of what’s now active, how enforcement works, and how to keep your cloud configuration healthy using our built-in optimization tools.
🚦 New Limits Enforced
Limits are now being enforced across Jira, Jira Service Management, and Jira Product Discovery for the following configuration areas:
- Field options: 20,000 options per field
- Work item security levels: 50 levels per space
- Permission grants: 50 grants per individual permission
- Releases / Versions: 15,000 active releases per space (archived releases excluded)
- Workflows: 150 workflows per workflow scheme
- Workflow statuses: 200 statuses per workflow
- Components: 10,000 components per space
- Priorities: 100 priorities per space
🛡️ What Happens If Your Space Reaches a Limit?
As a reminder, limits are designed to protect your data. With enforcement:
- Your existing data is never deleted or modified. Everything currently in place continues to operate without interruption.
- Impact is scoped strictly to administrative additions. If a space reaches a threshold, administrators will simply be prevented from adding new items of that specific type until usage is brought back under the limit.
- Standard users are unaffected. Regular issue creation, edits, transitions, and search continue operating normally.
🛠️ What To Do If You’re Approaching or Above a Limit
If you receive an in-product limit notification or want to proactively review your instance health:
- Use Site Optimizer: Navigate to Settings > System > Site Optimizer (available on Premium & Enterprise plans) to view live configuration reports across fields, schemes, roles, and components, and run bulk cleanups in just a few clicks.
- Follow Cleanup Best Practices: Refer to our step-by-step guides on cleaning out old data using Site Optimizer and data limits and guardrails in Jira Cloud.
- Planning a Cloud Migration? Entity limits are non-blocking for migrations. If your migrated site is near (above 90% usage) or at a limit after migration, Jira automatically applies a three-month exemption period for that entity upon completion, giving your administrators dedicated time to review and optimize configurations without disrupting onboarding.
- Need Temporary Assistance? If your team needs additional time to complete cleanup before a limit takes effect, contact Atlassian Support or your Technical Account Manager (TAM) to discuss a transition plan.
💬 Questions or Feedback?
Our goal is to ensure your Jira Cloud environment remains fast, maintainable, and reliable as your organization grows. Please leave your questions or feedback in the comments below!
Previous Announcements
Growing our investment in a faster, cleaner Jira - Atlassian
Empowering Jira admins to optimize usability at scale - Atlassian
