Welcome to QuotaWatch, an API quota monitoring and Jira governance solution designed to help administrators proactively monitor the health, scalability, and operational readiness of their Jira Cloud instance.

Before You Begin

Before using QuotaWatch, ensure that:

• You have Jira Administrator permissions.

• QuotaWatch has been installed from the Atlassian Marketplace.

• You have access to create or update Jira Automation rules (optional, but recommended for notifications).

• You have a project where monitoring alerts can be recorded.

Understanding the QuotaWatch Interface

QuotaWatch is organised into five primary sections.

For most administrators, the Overview page should be the starting point for daily monitoring.

Getting Started

Follow these steps to configure QuotaWatch after installation.

Step 1 – Open QuotaWatch

1. Sign in to Jira Cloud with administrator access.

2. From the Jira navigation menu, select Apps.

3. Open QuotaWatch.

The Overview dashboard will open automatically.

Step 2 – Configure Alert Thresholds

Open Settings → Alert Rules.

Choose the warning threshold that best matches your organisation's workload.

Lower thresholds provide earlier warnings.

Higher thresholds reduce alert frequency.

The default configuration is suitable for most Jira environments.

Step 3 – Configure Monitoring

Switch to Settings → Monitoring Configuration.

Configure the following:

• Monitoring Issue Key

• Data Limits Scan Scope

The monitoring issue acts as the central location where QuotaWatch publishes operational alerts.

Step 4 – Test Notifications

After saving your configuration:

1. Select Send Test Signal.

2. Confirm that a test comment appears on the configured monitoring issue.

3. Verify that your Jira Automation rule delivers the notification successfully.

Testing confirms that monitoring is working correctly before production alerts are required.

Step 4 – Review Your Environment

The Overview page provides an immediate summary of your Jira environment.

Review the following sections:

• API Health

• Hourly API Quota

• Burst Capacity

• Governance Score

• Recommendations

If everything is healthy, no action is required.

If warnings appear, use the remaining tabs to investigate further.

Step 5 – Review API Activity

Open the API Activity page.

This page helps answer questions such as:

• Who is consuming the most API quota?

• Which projects generate the most activity?

• Are Marketplace apps or automation rules contributing to increased API usage?

• Are traffic spikes expected or unusual?

If API usage is higher than expected, use this page to identify likely contributors before adjusting alert thresholds.

Step 6 – Review Data Limits Governance

Open the Data Limits Governance page.

QuotaWatch evaluates your Jira configuration against Atlassian's recommended platform limits.

Review:

• Overall Site Capacity

• Configuration Drift

• Space-Level Guardrails

• Site-Wide Guardrails

• Recommendations

This page helps administrators identify configuration growth before it becomes difficult to manage.

Step 7 – Review Historical Trends

Open the History page.

This page contains two historical views:

API Rate Limiting History

Review historical API monitoring snapshots to identify recurring spikes or previous incidents.

Data Limits Drift History

Review how your Jira configuration has changed between governance assessments.

Understanding historical trends makes it easier to identify recurring operational issues and validate cleanup activities.

How QuotaWatch Monitors Your Jira Environment

QuotaWatch continuously monitors two different aspects of your Jira Cloud instance.

API Rate Monitoring

QuotaWatch monitors Jira Cloud API usage and helps administrators understand:

• Current API health

• Historical API trends

• API traffic patterns

• High activity periods

• Potential API throttling risks

This helps prevent unexpected failures caused by API limits.

Data Limits Governance

QuotaWatch also monitors Jira configuration growth.

Examples include:

• Projects

• Issues

• Workflows

• Statuses

• Custom Fields

• Components

• Releases

• Security Levels

• Permission Grants

Rather than waiting until configuration becomes difficult to manage, administrators receive visibility into long-term platform growth.

Frequently Asked Questions

How often should I review QuotaWatch?

For most organisations:

• Review the Overview page daily.

• Review API Activity when API alerts occur.

• Review Data Limits Governance monthly.

• Review History during operational reviews or after significant Jira changes.

Does QuotaWatch affect Jira performance?

No.

QuotaWatch is designed to monitor your Jira environment efficiently while minimising its own API usage.

Monitoring frequency adapts to the current health of your environment to reduce unnecessary activity.

Can QuotaWatch identify the exact source of every API request?

QuotaWatch provides administrators with actionable insights into API activity and likely contributors.

These insights help identify users, projects, automation, and applications associated with increased API demand.

Can QuotaWatch send notifications to Slack or Microsoft Teams?

Yes.

QuotaWatch integrates with Jira Automation, allowing alerts to be forwarded to Slack, Microsoft Teams, PagerDuty, email, webhooks, and other supported notification channels.