🚀 New in QuotaWatch: Monitor Jira Data Limits Before They Become a Problem

[#1]

As Jira administrators, we spend a lot of time monitoring projects, workflows, automation, and integrations.

But there's another aspect of Jira health that's often overlooked until it starts causing administrative headaches:

Jira Data Limits & Guardrails.

Atlassian already publishes recommended limits for many Jira configuration objects to help customers maintain a healthy and scalable Jira instance.

These include areas such as:

• Custom Fields

• Workflows

• Statuses

• Components

• Versions

• Projects

• Permission Grants

• Security Levels

• And more...

The list continues to evolve as Atlassian introduces additional guardrails for Jira Cloud.

📖 Learn more about Atlassian's guidance here

---

The Problem

Most Jira administrators don't continuously monitor these limits.

Configuration grows gradually.

A few custom fields today.

A few projects next month.

Another workflow during the next implementation.

Over time, Jira becomes more complex to administer, but there's no easy way to understand how healthy your instance actually is.

For Jira Standard customers, there isn't a built-in dashboard that brings all these guardrails together in one place.

For Jira Premium, Site Optimizer provides valuable recommendations, but it doesn't proactively notify administrators as configuration approaches Atlassian's recommended thresholds.

That means many teams discover governance issues only during migrations, performance investigations, or platform reviews.

---

That's Why We've Expanded QuotaWatch

QuotaWatch started as an API Rate Limit monitoring solution, helping organisations monitor Jira Cloud API usage before integrations and automation begin failing.

Today, it's trusted by organisations that rely on Jira for business-critical workflows.

Now we're extending QuotaWatch beyond API monitoring.

We've added Jira Data Limits Governance, allowing administrators to continuously monitor the structural health of their Jira instance from the same application.

---

What You Can Monitor

QuotaWatch continuously evaluates important Jira configuration areas, including:

✅ Projects

✅ Issues

✅ Custom Fields

✅ Components

✅ Versions

✅ Workflows

✅ Statuses

✅ Work Types

✅ Permission Grants

✅ Security Levels

…and additional governance metrics as Atlassian expands its recommendations.

Everything is presented in a single dashboard, so you don't need to manually collect information from multiple administration screens.

---

Introducing the Site Health Score

One feature we're particularly excited about is the new Site Health Score.

Instead of looking at dozens of individual metrics, QuotaWatch provides a single score that reflects the overall governance health of your Jira instance.

This helps answer questions like:

• Is our Jira environment growing sustainably?

• Should we schedule cleanup activities?

• Are we approaching Atlassian's recommended limits?

• Is our Jira instance healthy enough for future growth?

The score also makes it easier to communicate Jira health with leadership and stakeholders who may not be familiar with Jira administration.

If your score starts trending downward, it may be the right time to review your Jira configuration—or engage an Atlassian Solution Partner to assess your instance and recommend improvements before governance issues become larger operational challenges.

---

Track Configuration Drift

Knowing today's numbers is useful.

Knowing what changed is even more valuable.

QuotaWatch now tracks the five most significant governance changes between assessments, helping administrators quickly identify:

• Rapid configuration growth

• Newly created projects

• Workflow expansion

• Changes to key Jira configuration

• Governance trends over time

Instead of manually comparing exports or spreadsheets, you can immediately see how your Jira environment is evolving.

---

Available for Jira Standard Too

One of our goals was to make governance accessible to every Jira Cloud customer.

Jira Standard customers can now monitor their Jira configuration health without building custom scripts, scheduled jobs, or internal dashboards.

Everything is available directly inside Jira.

No maintenance.

No custom code.

No manual reporting.

---

Still Includes API Rate Limit Monitoring

Everything QuotaWatch already offered remains available.

You can continue monitoring:

• Hourly API quota

• Burst Capacity

• API Activity

• Historical rate limit trends

• Alerting through Jira Automation

Now, alongside API health, you can also monitor the long-term governance health of your Jira instance.

---

We'd Love Your Feedback

This is the first release of our Data Limits Governance capability, and we'd love to hear how you're managing Jira growth today.

• Which governance metrics would you like us to add next?

• What information do you currently collect manually?

• Which data limits have caused the biggest challenges for your organisation?

Your feedback will help shape future releases.

---

📌 QuotaWatch is available on the Atlassian Marketplace. If you're already using it for API rate limit monitoring, update to the latest version to start exploring the new Data Limits Governance features. If you're new to QuotaWatch, this is a great time to see how it can help you monitor both API health and Jira governance from a single app.

[MeghnaP_LogicLemur Labs]

For Jira Standard admins specifically, this closes a real gap. Site Optimizer's governance view is a Premium-only feature, and the alternative — pulling field/workflow/status counts via the REST API on a scheduled script — means building and maintaining your own polling job, error handling, and threshold alerting from scratch just to get visibility Atlassian already recommends but doesn't surface on Standard plans.

QuotaWatch packages that as a ready dashboard: no script to write, no job to schedule, no API client to maintain. The Site Health Score is useful for the same reason — it turns raw guardrail numbers (custom fields, workflows, statuses, permission grants, etc.) into one number that's easier to report upward than a spreadsheet of thresholds.

Worth checking for any team on Standard currently tracking this manually or not tracking it at all.

PS: If you're already monitoring API rate limits with QuotaWatch, the Data Limits Governance view is in the same app — update to see it, no separate install needed.

[MeghnaP_LogicLemur Labs]

Timing note on the September 2026 enforcement:

Worth flagging for anyone reading this in the next few weeks: the second wave of Jira Cloud hard limits takes effect this September. Unlike the March 2026 wave (fields, work types), this one covers a broader set of configuration objects:

• Workflows: 150 per space
• Workflow statuses: 200 per workflow
• Priorities: 100 per space
• Field options: 20,000 per field
• Components: 10,000 per space
• Releases: 15,000 per space
• Permission grants: 50 per permission
• Work item security levels: 50 per space

These are hard limits, not guardrails — once reached, Jira blocks further changes to that object type until you're back under threshold. Sites that have been live for several years and accumulated workflow sprawl or legacy permission schemes are the most exposed.

If you haven't audited these specific object counts yet, QuotaWatch's Data Limits Governance dashboard maps directly to this list, so you can see where you stand against each threshold before September rather than after. Given the enforcement date is fixed, the useful window for cleanup is now, not once changes start getting blocked mid-sprint.