QuotaWatch for Jira: Data Limits Governance
The Data Limits Governance page helps Jira administrators monitor the long-term health and scalability of their Jira Cloud instance.
As Jira grows, the number of projects, workflows, custom fields, statuses, and other configuration objects also increases. While this growth is expected, unmanaged growth can make Jira more difficult to administer, impact usability, and eventually approach Atlassian's recommended platform limits.
QuotaWatch continuously evaluates your Jira configuration and highlights areas that may require attention before they become operational problems.
Unlike the Overview page, which focuses on real-time API health, the Data Limits Governance page focuses on the overall structure and maintainability of your Jira environment.
Why Use This Page?
A well-managed Jira instance is easier to maintain, performs more consistently, and scales more effectively as your organisation grows.
This page helps you answer questions such as:
Are we approaching Atlassian's recommended limits?
Which projects require cleanup?
Which configuration objects are growing the fastest?
Are there unused projects consuming platform capacity?
What should administrators prioritise during maintenance?
By reviewing this page regularly, administrators can identify configuration issues early and avoid large-scale cleanup projects later.
Understanding the Governance Dashboard
The dashboard is organised into four main sections:
Overall Site Capacity
Configuration Drift
Space-Level Guardrails
Site-Wide Guardrails
Together, these sections provide a complete view of your Jira configuration health.
Overall Site Capacity
The Overall Site Capacity card provides a high-level summary of your Jira environment.
Rather than reviewing dozens of individual metrics, this score gives administrators a quick indication of whether their Jira instance is operating comfortably within recommended limits.
The card includes:
Overall Site Capacity Score
Current health status
Number of guardrails currently passing
Number of guardrails requiring attention
This score should be treated as a starting point for investigation rather than a replacement for reviewing the individual guardrails.
Capacity Score
The Capacity Score represents the overall health of your Jira configuration.
A higher score indicates that your Jira instance remains comfortably within Atlassian's recommended limits.
A lower score suggests one or more areas should be reviewed.
Typical interpretations are:
Score | Health | Recommendation |
|---|---|---|
90–100 | Excellent | No immediate action required. |
75–89 | Good | Review highlighted recommendations during regular maintenance. |
50–74 | Fair | Plan cleanup activities before continued growth. |
Below 50 | Needs Attention | Review configuration as soon as possible. |
The score should be viewed as a planning tool rather than a performance measurement.
Run Assessment Scan
The Run Assessment Scan button performs a fresh analysis of your Jira configuration.
Use this option whenever:
New projects have been created.
Large migrations have completed.
Significant administration changes have been made.
You want to verify the latest configuration health.
Running a scan refreshes all governance metrics displayed on the page.
Configuration Drift
Jira environments constantly evolve.
Projects are created.
Workflows change.
Fields are added.
Permissions are updated.
Configuration Drift helps administrators understand how the Jira environment has changed over time.
After each assessment, QuotaWatch compares the latest configuration with the previous assessment and highlights meaningful changes.
Examples include:
New workflows
Additional custom fields
Project growth
Permission changes
Configuration increases
If no significant changes are detected, the page confirms that the environment remains consistent with the previous assessment.
This makes it easier to identify unexpected administrative changes across large Jira environments.
Space-Level Guardrails
Space-Level Guardrails focus on configuration limits within individual Jira projects.
Large projects often accumulate configuration over time.
Monitoring these limits helps prevent individual projects from becoming difficult to manage.
Custom Fields
Displays projects approaching Atlassian's recommended limit for custom fields.
Large numbers of custom fields can increase administration complexity and make issue screens harder to maintain.
Consider reviewing:
Unused fields
Duplicate fields
Project-specific fields that can be consolidated
Components
Displays projects with large numbers of components.
Components are useful for organising work, but excessive numbers can make project administration more difficult.
Review components periodically and archive or remove entries that are no longer required.
Releases
Shows projects containing large numbers of releases or versions.
Projects with many historic releases can become difficult to navigate.
Review completed releases regularly and archive or consolidate where appropriate.
Work Types
Displays projects approaching recommended limits for work item types.
A large number of work types often indicates duplicated processes or inconsistent project configuration.
Review work types periodically to ensure they remain meaningful and actively used.
Site-Wide Guardrails
Site-Wide Guardrails monitor configuration shared across the entire Jira instance.
Unlike project-specific metrics, these values affect every project within your organisation.
Issues
Displays the total number of issues currently stored in Jira.
Growing issue counts are expected over time.
This metric primarily helps administrators understand overall platform growth.
Projects
Shows the total number of Jira projects.
Unused projects continue to consume administrative overhead even if they contain little or no work.
Review inactive projects regularly.
Archive or remove projects that are no longer required.
Workflows
Displays the number of workflows configured across the Jira site.
Large workflow libraries often indicate duplicated configurations.
Where possible, reuse existing workflows rather than creating new variations.
Statuses
Shows the total number of workflow statuses.
Too many statuses can make workflows difficult for users to understand.
Aim for simple, reusable workflows whenever possible.
Priorities
Displays the number of issue priorities configured.
Most organisations require only a small set of priorities.
Review additional priorities to ensure they provide genuine business value.
Security Levels
Displays the number of configured issue security levels.
Security levels should remain simple and easy to manage.
Complex permission structures can increase administrative effort.
Permission Grants
Shows the number of configured permission grants.
Review permission configurations periodically to ensure they remain appropriate as teams and projects evolve.
Recommendations
QuotaWatch automatically identifies opportunities to improve the health of your Jira environment.
Recommendations appear only when administrator attention is required.
Typical recommendations include:
Projects approaching recommended limits.
Large configuration growth.
Opportunities to consolidate configuration.
Unused administrative objects.
Projects requiring cleanup.
Each recommendation explains:
What was detected.
Why it matters.
What action is recommended.
Administrators should review recommendations during regular maintenance cycles.
Untracked Limits
Some Jira configuration limits cannot be assessed automatically because they are not currently exposed through available platform APIs or require operations that would be expensive to perform continuously.
QuotaWatch lists these limits separately so administrators remain aware of them during periodic governance reviews.
Where appropriate, these limits should be reviewed manually as part of regular Jira administration.
Best Practices
✔ Run a governance assessment after major Jira migrations.
✔ Review recommendations during monthly administration reviews.
✔ Archive inactive projects whenever possible.
✔ Consolidate duplicate workflows and custom fields.
✔ Keep Jira configuration simple and consistent across projects.
✔ Review configuration growth before creating additional administrative objects.
✔ Use this page as part of regular Jira health checks rather than waiting until limits are reached.
Example Governance Review
A monthly governance review might follow these steps:
Open the Data Limits Governance page.
Review the Overall Site Capacity score.
Check whether any guardrails require attention.
Review Configuration Drift to understand recent changes.
Investigate projects approaching recommended limits.
Review Ghost Projects for potential cleanup, check optimization options
Schedule maintenance activities where necessary.
Run another assessment after completing cleanup to verify improvements.
Following a regular review process helps keep Jira manageable as your organisation grows.
Frequently Asked Questions
Does reaching a recommended limit mean Jira will stop working?
No.
The values displayed by QuotaWatch are based on Atlassian's recommended operational limits.
Approaching a recommendation does not necessarily mean Jira will stop functioning, but it may indicate that administrative complexity is increasing and future growth should be planned carefully.
Why are inactive projects shown?
Inactive projects still contribute to the overall size and complexity of your Jira instance.
Removing or archiving projects that are no longer required helps maintain a cleaner and more manageable environment.
Should every recommendation be acted on immediately?
Not necessarily.
Recommendations are intended to help administrators prioritise maintenance activities.
Review each recommendation within the context of your organisation's requirements before making changes.
Does a high Capacity Score guarantee good performance?
No.
The Capacity Score reflects how closely your Jira configuration aligns with recommended governance practices.
Application performance is also influenced by factors such as automation, Marketplace apps, indexing, workflows, and user activity.
How often should I review this page?
For most organisations, reviewing the Data Limits Governance page once each month is sufficient, you can set the warning threshold and QuotaWatch will alert you when this threshold is crossed by the space level / site wise data limit. Also if you didn’t set the limit the default critical limit is 95%
Larger Jira environments or organisations undergoing rapid growth may benefit from more frequent reviews.
Related Pages
Continue exploring QuotaWatch using the following pages:
History – Review previous assessments, API incidents and historical trends.
Settings – Configure monitoring preferences and alert thresholds.
Administrator Tip: Treat the Data Limits Governance page as a proactive maintenance dashboard rather than a troubleshooting tool. Regular reviews help keep your Jira instance clean, scalable, and easier to manage, reducing the need for large-scale cleanup projects in the future.