QuotaWatch for Jira: History
The History page provides a historical view of your Jira environment, allowing administrators to review both API monitoring history and configuration changes over time.
While the Overview page shows the current health of your Jira instance, the History page helps answer an equally important question:
How has my Jira environment changed over time?
Historical information is essential for troubleshooting recurring API issues, validating governance improvements, understanding platform growth, and supporting operational reviews.
The History page contains two sections:
API Rate Limiting History
Data Limits Drift History
Together, these views provide a complete operational audit trail of your Jira Cloud instance.
API Rate Limiting History
The API Rate Limiting History section records historical API monitoring snapshots collected by QuotaWatch.
Instead of only displaying the current API health, this page allows administrators to review previous monitoring periods, identify recurring usage patterns, and investigate incidents that are no longer visible on the Overview dashboard.
This information is particularly valuable when troubleshooting intermittent issues or validating the impact of changes made to integrations, Marketplace apps, or automation rules.
Why Use API Rate Limiting History?
API usage naturally changes throughout the day.
Large imports, automation rules, software deployments, and user activity can all influence API consumption.
Reviewing historical data helps administrators answer questions such as:
When did API usage increase?
How often do warning or critical events occur?
Are API spikes happening at the same time every day?
Did recent changes improve API utilisation?
Is API demand increasing over time?
Rather than relying on memory or isolated incidents, administrators can review actual monitoring history.
Snapshot Summary
The summary cards at the top of the page provide a quick overview of the currently displayed monitoring history.
These metrics update automatically when filters are applied.
Snapshots in View
Displays the total number of monitoring snapshots currently shown.
This indicates how much historical information is included in the current view.
Incidents
Shows the number of monitoring periods where API usage exceeded warning or critical thresholds.
A consistently increasing incident count may indicate growing API demand or inefficient integrations.
Worst Usage
Displays the highest API utilisation recorded within the selected time period.
This helps administrators quickly identify the most demanding monitoring period.
Filtering Historical Data
Filters allow administrators to focus on the information most relevant to their investigation.
Status Filter
Filter snapshots by health status.
Typical options include:
Healthy
Warning
Critical
This is useful when reviewing only periods where administrator attention was required.
Pool Filter
QuotaWatch monitors different API limit categories.
Use this filter to review a specific monitoring pool, such as hourly API quota or burst capacity.
Date Filter
Limit results to a today or yesterday
Filtering by date makes it easier to compare activity before and after administrative changes.
Snapshot Details
Each row in the history table represents a monitoring snapshot.
The table provides a complete record of API health at a specific point in time.
Timestamp
Displays when the monitoring snapshot was collected.
Use this information to correlate API activity with:
Scheduled automation
Marketplace upgrades
Software deployments
Data imports
User activity
Status
Indicates the overall API health during that monitoring period.
Status | Meaning |
|---|---|
Healthy | API usage remained within normal operating limits. |
Warning | API usage approached configured alert thresholds. |
Critical | API usage reached or exceeded safe operating limits. |
Pool
Identifies the API limit category being monitored.
This helps distinguish between different types of API limits when investigating incidents.
Quota
Displays the total API capacity available during the monitoring period.
Remaining
Shows how much API capacity remained when the snapshot was recorded.
Lower remaining values generally indicate heavier API usage.
API Usage
Displays the percentage of API quota consumed during the monitoring period.
Higher percentages indicate increased API demand.
Activity
Shows the relative level of Jira activity associated with that monitoring snapshot.
This helps administrators determine whether increased API usage corresponds with expected business activity.
Export Monitoring History
The Export CSV option allows administrators to download the currently displayed monitoring history.
Exported reports are useful for:
Operational reporting
Capacity planning
Incident investigations
Sharing information with stakeholders
Long-term trend analysis
Clear History
The Clear History option removes previously collected monitoring snapshots.
This action is typically used when:
Resetting monitoring after testing
Establishing a new baseline
Removing historical test data
Before clearing history, consider exporting reports if historical information may be required later.
Data Limits Drift History
The Data Limits Drift History section records how your Jira configuration changes over time.
While the Data Limits Governance page shows the current state of your Jira configuration, Drift History explains how that state evolved.
This allows administrators to understand configuration growth, validate governance improvements, and investigate unexpected administrative changes.
Why Use Drift History?
Jira environments continually evolve.
Projects are created.
Workflows change.
Custom fields are added.
Permissions are updated.
Issue types evolve.
Without historical comparisons, administrators only see the current state of Jira.
Drift History provides the missing context by recording configuration changes between governance assessments.
Understanding Configuration Drift
Configuration Drift refers to any difference detected between two governance assessments.
Examples include:
New projects
Additional workflows
New custom fields
Status changes
Permission updates
Archived projects
Deleted configuration objects
Tracking these changes helps administrators understand how Jira is evolving over time.
Drift Summary
The Drift Summary provides a high-level overview of configuration changes detected during the selected assessment period.
Administrators can quickly determine:
How many configuration objects changed
Which categories experienced the most growth
Whether governance has improved or deteriorated
Which areas require review
Drift Details
Each row represents a detected configuration change.
The table provides enough information to understand exactly what changed without manually comparing governance reports.
Typical information includes:
Assessment Date
Shows when the governance assessment was performed.
Object Type
Identifies the type of Jira configuration that changed.
Examples include:
Projects
Custom Fields
Workflows
Statuses
Components
Versions
Issue Types
Permission Schemes
Security Schemes
Previous Value
Displays the value recorded during the previous governance assessment.
Current Value
Displays the latest value detected during the current assessment.
Change
Summarises what changed.
Examples include:
New project created
Workflow modified
Custom field removed
Status added
Component archived
Impact
Explains how the detected change may affect governance.
Examples include:
Informational
Monitor
Review Recommended
Attention Required
This helps administrators prioritise governance reviews.
Investigating Configuration Changes
A typical governance review follows these steps:
Open Data Limits Drift History.
Review the latest governance assessment.
Identify newly created configuration.
Review significant increases in configuration growth.
Validate that changes align with planned administration activities.
Investigate unexpected configuration growth.
Perform cleanup where appropriate.
Run another governance assessment to verify improvements.
Best Practices
✔ Review API Rate Limiting History whenever API alerts occur.
✔ Review Configuration Drift after every governance assessment.
✔ Compare historical trends rather than individual events.
✔ Export reports before major Jira maintenance activities.
✔ Archive unused projects and simplify configuration regularly.
✔ Validate governance improvements by comparing assessment history.
✔ Use historical information during operational reviews and internal audits.
Frequently Asked Questions
How is the History page different from the Overview page?
The Overview page displays the current health of your Jira environment.
The History page shows how that health has changed over time, allowing administrators to identify trends, investigate incidents, and review configuration changes.
What is Configuration Drift?
Configuration Drift refers to any change detected between two governance assessments.
Examples include new projects, updated workflows, additional custom fields, archived projects, or permission changes.
Does every configuration change require action?
No.
Many changes are part of normal Jira administration.
Drift History helps distinguish expected changes from those that may require governance review.
When should I export history?
Export history before:
Major Jira upgrades
Platform migrations
Cleanup activities
Quarterly governance reviews
Internal compliance or audit exercises
Should I clear monitoring history regularly?
No.
Historical information becomes more valuable over time because it helps identify recurring trends and measure the effectiveness of governance improvements.
Related Pages
Continue exploring QuotaWatch using the following pages:
Settings – Configure monitoring preferences, governance assessments, and alert thresholds.
Administrator Tip: The History page is more than an audit log. It provides the historical context needed to understand how your Jira environment is evolving. Regularly reviewing both API Rate Limiting History and Data Limits Drift History helps identify recurring operational issues, measure the success of cleanup activities, and maintain a healthy, scalable Jira Cloud instance over time.