More Jira Data Limits Are Coming in September: What to start doing now

[#1]

The first wave of Jira Cloud data limits landed in March - 700 fields and 150 work types per space. Now a second wave is coming in September, and this time it covers workflows, statuses, priorities, and more.

The catch: these items are harder to "just check" than a custom field. They're wired into JQL filters, automations, and dashboards you can't see from a single config screen.

Jira Cloud data limits: what's changing (this time)

Jira's September 2026 update adds hard limits including:

• 150 workflows per space
• 200 statuses per workflow
• 100 priorities per space

Plus additional caps on field options, components, releases, permission grants, and work item security levels.

Once a limit is hit, Jira blocks further changes until you clean up - same enforcement model as wave one.

How Optimizer's new Monitoring feature helps Admins stay in control

To help admins clean up statuses, priorities, and fields without guessing, Optimizer for Jira now includes Monitoring.

📡 Track Live Usage, Not Just a Snapshot

Add a status, priority, custom field, or other config item to monitoring, and Optimizer checks daily whether it's still being used - building a dated usage record over time, not a one-off guess.

🗑️ Delete with Confidence, Not Guesswork

No more chasing teams on Slack asking "does anyone still use this?" When the monitoring period ends, you'll know - and can delete straight from the Monitoring page with the same review safeguards as any other bulk action.

Why this matters for Jira Admins

• Avoid breaking a workflow, status, or filter that looked dead but wasn't
• Stop relying on team silence as your signal that something's unused
• Build a defensible, dated case for every deletion before September's limits bite
• Carry the momentum from your wave-one cleanup straight into wave two

It's the difference between deleting config and hoping for the best, versus deleting it because you know you can safely, without breaking anything.

Take action before September

Wave one gave admins a preview of what's coming. Wave two raises the stakes - and Monitoring is built specifically for the calls that are hardest to reverse.

If you already use Optimizer for Jira, add your at-risk statuses and priorities to Monitoring today.

👉 If you already use Optimizer for Jira, start monitoring problem fields now to see which you can safely trim ahead of September.

👉 If you don’t, you can try Optimizer for Jira for free from the Atlassian Marketplace.

Or, read here for the full breakdown!

[Henry Collins]

The workflow and status limits are the ones you should consider most because they're tied into so many automations and filters. Waiting until you hit the cap is asking for trouble. Tracking usage over time before deleting anything seems like the safest approach, especially in larger Jira instances where old configurations tend to pile up.

[Matthew Joslin_AppFox_]

@Henry Collins Really good point, thanks for adding this. Workflows and statuses are for sure the ones that feel most stressful. A stale custom field is usually contained, but a status or workflow can be quietly load-bearing across dozens of automations and saved filters without it being obvious from the config screen alone.