/
QuotaWatch 3.5

QuotaWatch 3.5

Welcome to QuotaWatch v3.5.0! This is our biggest architecture and feature upgrade since the original launch. This release brings an entirely new dimension of visibility to your Jira API quotas by answering the most important question: "Who is burning our quota?"

We’ve also rebuilt the underlying polling engine and storage mechanisms to ensure QuotaWatch remains perfectly frictionless, secure, and robust under enterprise traffic loads.

✨ New Features

🕵️‍♀️ The "Activity" Tab: Top Consumers Detective

Because Atlassian's rate limit headers don't specify who caused the limit to drop, we've built a new Activity Dashboard. By silently capturing high-intent Jira events in the background (Issue Created, Updated, Transitioned, etc.), QuotaWatch generates a "proxy" map of your site's busiest actors.

  • Top Projects: See which Jira projects are generating the heaviest background loads.

  • Top Users (and Bots!): Identifies your heaviest users. New automation detection logic automatically tags non-human traffic with an [App] lozenge, instantly revealing thirsty third-party integrations or runaway Jira Automation rules.

  • Top Actions: Shows the exact distribution of traffic types (e.g., are users mostly creating issues, or transition-spamming?).

📈 Visual Spike Detection

The Activity tab now features a 24-hour visual timeline of high-intent events. Our new heuristics engine constantly compares current traffic against a 24-hour rolling average, automatically flagging sudden "Traffic Spikes" so you can correlate API exhaustion with specific workflow events.

🛡️ Adaptive "Conservation" Polling Engine

QuotaWatch's mission is to protect your API limits, not consume them. We've introduced a dynamic polling engine that adapts to your site's health:

  • Conservation Mode: If usage is safely below 80% (🟢 Normal), the background monitor goes to sleep, only checking once every 60 minutes.

  • Standard Mode: When usage enters the warning zone (80–90%), checking increases to every 15 minutes.

  • High-Resolution Mode: If usage exceeds limits (90%+), the engine fires every 5 minutes to ensure instant alert delivery.

Feedback or Issues? Please reach out to the platform administration channel for support regarding the new Activity dashboards.