QuotaWatch for Jira : Settings
The Settings page allows Jira administrators to configure how QuotaWatch monitors their Jira Cloud environment and how administrators are notified when attention is required.
Rather than continuously monitoring every project or requiring administrators to manually review dashboards, the Settings page lets you customize alert behavior, define monitoring scope, and integrate QuotaWatch with Jira Automation for notifications.
The Settings page is divided into two sections:
Alert Rules
Monitoring Configuration
These settings only need to be configured once and can be updated whenever your monitoring requirements change.
Alert Rules
The Alert Rules section controls when QuotaWatch should notify administrators about potential API rate limiting or Jira governance issues.
Instead of waiting until Jira reaches a critical state, you can configure QuotaWatch to notify your team before limits become a problem.
Alert Threshold
The alert threshold determines when QuotaWatch considers API usage or governance capacity to require administrator attention.
Use the slider to select the warning threshold that best suits your environment.
For example:
Warning Threshold | Recommendation |
|---|---|
80–85% | Recommended for large Jira environments with many integrations. Provides early warning before limits are approached. |
86–90% | Suitable for most organisations. Balances early notification with reduced alert noise. |
Above 90% | Recommended only if occasional high API usage is expected and administrators prefer fewer alerts. |
Lower thresholds provide earlier visibility but may generate more notifications.
Higher thresholds reduce alert frequency but provide less time to investigate issues before limits are reached.
Warning Alerts
When API usage or governance capacity exceeds the configured warning threshold, QuotaWatch generates a warning event.
As Atlassian sends the rate limiting details only after 80% is reached; any warning configuration below will treat the warning value as 80 for API but the value will be applicable for the data limit goverance.
Warning alerts are intended to provide administrators with enough time to investigate before usage reaches critical levels.
Typical causes include:
Large imports
Increased automation activity
Marketplace app synchronisation
Bulk issue updates
Configuration growth
Critical Alerts
Critical alerts are generated when value cross 95% critical threshold.
Critical alerts indicate that Jira is approaching a state where Marketplace apps, automation rules, or integrations may begin experiencing API throttling.
Administrators should investigate these alerts as soon as possible.
Jira Automation Bridge
QuotaWatch is designed to work with Jira Automation, allowing organisations to deliver notifications through their existing operational workflows.
Instead of sending notifications directly to external services, QuotaWatch publishes alerts inside Jira.
Jira Automation can then forward those alerts to collaboration and incident management platforms.
This approach keeps QuotaWatch compliant with Atlassian's data residency requirements while giving organisations complete control over notification routing.
Configuring Alert Notifications
To configure automated notifications:
Open the Monitoring Configuration tab.
Select a dedicated monitoring issue.
Save the configuration.
Create a Jira Automation rule.
Configure the rule to respond to QuotaWatch alert comments.
Forward notifications to your preferred collaboration platform.
Once configured, QuotaWatch automatically publishes alert events whenever configured thresholds are exceeded.
Open Jira Automation Guide
If you're unfamiliar with Jira Automation, use the Open Jira Automation Guide link.
The guide provides step-by-step instructions for configuring an automation rule that forwards QuotaWatch alerts to external systems.
Here is the complete, single master reference table combining all API Rate Limit, System Test, Data Governance, and Site-Wide Usage alert categories.
Alert Category | Automation Condition ( | Trigger Event | Sample Comment Message |
|---|---|---|---|
API Rate Limit |
| Hourly API point usage exceeds configured alert threshold (e.g. 85%) |
|
API Rate Limit |
| Hourly API quota points completely exhausted (HTTP 429 received) |
|
API Rate Limit |
| Per-second concurrent request burst limit reached |
|
API Rate Limit |
| Single issue updated > 20 times within 2 seconds |
|
System Test |
| Admin clicks "Send Test Signal" button in Settings |
|
Data Governance |
| Entity count (e.g. Custom Fields > 700) exceeds Atlassian limit |
|
Data Governance |
| Empty or inactive projects found consuming space quota |
|
Data Governance |
| Orphaned or unlinked schemes detected after project deletion |
|
Site-Wide Usage |
| Total site workflows approach or exceed recommended max (150) |
|
Site-Wide Usage |
| Global status definitions approach recommended max (200) |
|
Site-Wide Usage |
| Permission grants per scheme approach recommended max (50) |
|
Site-Wide Usage |
| Total site projects (spaces) approach recommended max (8,400) |
|
Site-Wide Usage |
| Priority definitions approach recommended max (100) |
|
Site-Wide Usage |
| Issue security levels approach recommended max (50) |
|
Site-Wide Usage |
| Total site issue volume reaches 80%+ of recommended max (10M) |
|
Monitoring Configuration
The Monitoring Configuration tab determines what QuotaWatch monitors and where operational alerts are published.
These settings should be configured during the initial setup of QuotaWatch.
Monitoring Issue Key
QuotaWatch uses a dedicated Jira issue as its communication channel for alert events.
Rather than creating new issues for every alert, QuotaWatch publishes monitoring events to the selected issue.
This issue acts as a central operational record for:
API alerts
Governance alerts
Monitoring events
Test notifications
Using a dedicated monitoring issue keeps alert activity organised and simplifies automation.
Selecting a Monitoring Issue
Enter the Jira issue key that should receive QuotaWatch alerts.
For example:
OPS-12Most organisations create a dedicated operational issue specifically for monitoring alerts.
Using a dedicated issue prevents operational notifications from being mixed with normal project work.
Send Test Signal
After configuring the monitoring issue, select Send Test Signal.
QuotaWatch immediately publishes a sample monitoring alert to the configured issue.
This allows administrators to verify that:
The monitoring issue is configured correctly.
Jira Automation is working.
Notifications are delivered successfully.
External integrations receive alerts.
Testing is recommended whenever monitoring configuration changes.
IMPORTANT PERMISSION REQUIREMENT
The QuotaWatch application itself must have "Add Comments" permission in the project where your monitoring issue resides. If it doesn't, the app won't be able to post the warning comment. The Test Signal buttons tests whether you have permission, but the automated poller needs the app to have permission.
Data Limits Scan Scope
QuotaWatch can assess governance across your Jira environment in different ways.
The Data Limits Scan Scope determines which projects are included during governance assessments.
Track All Spaces
Selecting Track all spaces instructs QuotaWatch to assess every accessible Jira project across the site.
This option is recommended for most organisations because it provides a complete governance assessment.
Use this option when:
Performing organisation-wide governance reviews.
Monitoring overall Jira growth.
Preparing for platform audits.
Reviewing platform health.
Selected Spaces
For larger Jira environments, administrators may choose to monitor only specific projects.
Monitoring a smaller scope can:
Reduce assessment time.
Focus governance reviews on business-critical projects.
Exclude archived or temporary projects.
Simplify governance reporting.
This option is useful when different teams manage separate Jira environments.
Configuration Best Practices
To get the most value from QuotaWatch:
✔ Configure a dedicated monitoring issue.
✔ Test notifications before relying on them in production.
✔ Use Jira Automation instead of creating duplicate notification workflows.
✔ Select an alert threshold appropriate for your organisation's workload.
✔ Review alert thresholds periodically as API usage changes.
✔ Monitor the entire Jira site unless you have a specific reason to limit the assessment scope.
✔ Re-run a test signal whenever notification rules are modified.
Example Initial Setup
A recommended setup for a new QuotaWatch installation is:
Open Settings.
Configure the warning threshold.
Leave the critical threshold at the default value.
Switch to Monitoring Configuration.
Enter a dedicated monitoring issue (for example,
OPS-12).Select Track all spaces.
Save the configuration.
Send a test signal.
Create a Jira Automation rule to forward alerts to Slack or Microsoft Teams.
Confirm that the notification is successfully received.
Once complete, QuotaWatch will automatically monitor your Jira environment and notify your team whenever configured thresholds are exceeded.
Frequently Asked Questions
Why does QuotaWatch use a monitoring issue?
Using a dedicated monitoring issue allows Jira Automation to manage notification delivery.
This keeps alerts organised, supports multiple notification channels, and aligns with Atlassian's security and data residency practices.
Can I send alerts directly to Slack?
QuotaWatch uses Jira Automation as the notification bridge.
Once a Jira Automation rule is configured, alerts can be forwarded to Slack, Microsoft Teams, PagerDuty, or any system supported by Jira Automation.
Should I monitor all projects?
For most organisations, yes.
Monitoring all projects provides the most accurate view of your Jira environment.
If your organisation manages multiple independent business units, you may choose to monitor only selected projects.
How often should I test notifications?
Test notifications whenever:
Monitoring settings change.
Jira Automation rules are updated.
New notification destinations are configured.
Administrators change the monitoring issue.
Can multiple administrators modify the settings?
Yes.
Whenever settings are saved, QuotaWatch records the administrator and the time of the last update, providing a simple audit trail for configuration changes.
Related Pages
Continue exploring QuotaWatch using the following pages:
Administrator Tip: Configure the Settings page immediately after installing QuotaWatch. A properly configured monitoring issue, alert threshold, and Jira Automation rule ensure your team receives timely notifications and can respond to API or governance issues before they impact users.