ClaervoAdministrator guide
See how close every space, scheme and workflow is to Jira's configuration limits, then clean up safely with evidence and rollback.
1. Install and open
Install the app from Atlassian Marketplace for a Jira Cloud site. A Jira administrator opens Claervo Limits Guard from Jira administration → Apps.
2. Run the first scan
Select Scan now. The scan reads spaces, fields, schemes, workflows, statuses, releases, components and priorities in short batches that respect Jira's request budget. A daily background scan keeps the data fresh and writes a snapshot for trends.
3. Read the overview
The overview ranks every space, permission scheme, workflow scheme, workflow and field by usage against its limit. Warning starts at 75% and critical at 90% by default; rows link straight to the Jira administration page.
4. Spaces and schemes
Spaces shows fields, work types, security levels, releases, components and priorities per space. Schemes & workflows shows grants per permission, workflows per scheme, statuses per workflow and options per field.
5. Clean up safely
Cleanup lists unused fields, fields without context, duplicate field names, unused statuses, inactive workflows, stale releases, empty components and redundant permission grants, each with evidence. Select rows that share an action and confirm. Every action is re-checked against live Jira right before it runs.
6. Trends
Trends turns daily snapshots into a sparkline per limit and a projection of days until the limit at the recent pace.
7. Audit and rollback
Audit records every scan, cleanup action, dismissal and rollback with the acting administrator's account ID. Removed permission grants can be restored from the audit row. CSV exports are available for usage, findings and the audit trail.
8. Settings
Adjust warning and critical thresholds, unused-field and stale-release ages, excluded field and space IDs, the request budget per batch, spaces per scan and snapshot retention. Reset app data removes everything the app stored.
Known limits
Scheme-based limits apply to company-managed projects; team-managed projects are counted where the Jira API exposes the data. Work item counts are approximate. Limit values follow Atlassian's published figures and may change with Jira releases.