ClaervoKnow when Jira will stop you, and what to clean first.
Jira Cloud enforces configuration limits on every plan from September 2026. Limits Guard measures usage against all twelve, trends it daily, and cleans safely: every fix re-checks live state and can be rolled back.
Listing is in Atlassian review; installation opens once approved. from $1.20 per user / month above 10 users; up to 10 users free.
What it does
Twelve limits
Fields, work types, field options, security levels, permission grants, releases, workflows, statuses, components, priorities, spaces and work items.
Findings
Unused fields, duplicate fields, empty components, stale releases, redundant permission grants, oversized schemes.
Safe cleanup
Every action is re-validated against live Jira and recorded; permission grants can be restored.
Trends
Daily snapshots show how fast you approach each limit.
What it reads
- Configuration objects: fields, schemes, workflows, statuses, releases, components, permission grants
- Approximate work item counts
What it never touches
- Work item content, comments or attachments
- User profiles beyond account ids on grants
- Anything outside Atlassian
Scopes and why
| read:jira-work | Count work items and check usage before a change |
| manage:jira-configuration | Read fields, workflows, schemes; apply confirmed cleanup |
| manage:jira-project | Releases and components per project |
| storage:app | Findings, snapshots and audit trail |
Inside the app
