Don't miss the latest on expanded Jira limits, guardrails, and data management tools

[#1]

Hi Jira Community!

I wanted to share this article I posted in our Enterprise Community group last week about how we are continuing our investment in improving how you work in Jira, Jira Service Management, and Jira Product Discovery at scale, with:

• New limits: Starting September 2026, the Jira Cloud family of apps will enforce hard limits on several data types, listed below.

• New guardrails: You asked, we listened, and more guardrails are here to help you understand best practices and recommended thresholds for data volume and configuration.

• Enhanced data management tools: We are rolling out improved data cleanup tools available to all customers to help you find and easily manage unused or outdated data.

Check out the full post to learn more and don't forget to join the enterprise community group if your org has large, complex sites! 

[__ Jimi Wikman]

Just a heads up for those that just read the September date:

"Starting in March 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."

Is this what you mean by "hard limits"? I am asking because in the past, we have, for example, seen boards stop functioning if the limits have been breached, which was a denial of service, as it was not a known limitation at the time.

So, exactly what will happen when all of these limitations are breached, and when/how do we get notified in the UI that these limitations exist?