New Jira Data Limits Are Coming in February: What Admins Need to Know

[#1]

Atlassian has announced new Jira Cloud data limits starting in February, with some of them being strictly enforced. For Jira admins, this means one thing: if your projects are already close to these thresholds, future configuration changes may be blocked.

Instances that have grown over time - with unused custom fields, legacy issue types, and one-off configurations - are most at risk. The key now is visibility and action before the limits are enforced.

Jira Cloud data limits: what’s changing

Atlassian is introducing hard limits and guardrails to protect Jira performance at scale, including:

• 700 fields per company-managed project (hard limit)
• 150 issue types per company-managed project (hard limit)
• Site-level guardrails for overall configuration size

Once a hard limit is reached, Jira will prevent additional changes, even when there’s a legitimate business need. Atlassian’s guidance is clear: admins should proactively optimise now rather than react later.

How Optimizer for Jira helps Admins stay in control

To support Jira admins through these changes, Optimizer for Jira now includes functionality aligned directly with Atlassian’s data-limit announcement.

Instead of manually counting fields or exporting configs, admins get clear, actionable insight straight away.

🔍  Projects Nearing Field Limit Health Check

Quickly identify projects approaching (or exceeding) the 700-field limit, so you know exactly where cleanup is required first.

📊  Field Count Visibility Per Project

A new Field Count column shows how many fields each project is using, making it easy to spot high-risk projects without extra effort.

Why this matters for Jira Admins

These updates help you:

• Avoid hitting enforced Jira limits unexpectedly
• Prioritise field cleanup where it will have the biggest impact
• Keep projects flexible as requirements change
• Maintain performance and admin sanity at scale

It’s about staying ahead of configuration debt - not discovering it when Jira says “no more.”

Take action before February

Preparing now is far easier than being blocked later. The new Jira data limits are coming whether you’re ready or not.

The difference is whether you’ll be reacting under pressure, or managing them confidently.

👉 If you already use Optimizer for Jira, run the new health checks to see which projects are at risk.

👉 If you don’t, you can try Optimizer for Jira for free from the Atlassian Marketplace and get immediate visibility into how prepared your instance is.

For a full breakdown and a video walkthrough of Atlassian’s announcement and Optimizer’s new capabilities:
🔗 https://www.appfox.io/blog/new-atlassian-data-limits-how-optimizer-for-jira-will-help-your-teams/

🎥 https://youtu.be/WpOgRuv-8MM

[James Fama]

Thank you for the informative article.

We have recently reviewed these upcoming limits, and we are concerned that we may not have sufficient time to properly assess more than 1000 projects.

While the Site Optimizer tool is mentioned, its underlying operations are not fully clear to us. In a production environment, using it without a deeper understanding could risk impacting our existing configuration framework. Implementing the necessary changes will therefore require careful planning and thorough testing on our side.

Given that Jira administrators already manage a high volume of concurrent requests and changes, it would be extremely helpful if Atlassian could consider extending the timeframe for these changes.

This article is the first time we have been made aware of this update; we have not received any prior communication from our Atlassian representative.

[David Woo]

Please confirm whether marketplace apps are also included in this data limits?  Or are they exempt from this limitation.  Is there a baseline template that we can leverage to compare default fields and issueTypes to new fields/issueTypes from either the marketplace apps or from us?  And Is this going to be isolated or will other components be impacted like workflows, etc.....?