Jira Cloud · Runs on Atlassian · Zero egress · Rovo agent
Jira Cloud Limits Forecast and Safe Cleanup
Jira Cloud now enforces limits on fields, work types, options, security levels, grants, releases, workflows, statuses, components and priorities. LimitRadar shows how close every space, scheme and field is to each limit, forecasts when Jira will block the next change, and helps you clean up safely with a preview, a simulation and undo.
Built on Atlassian Forge and distributed through Atlassian Marketplace. Works on every Jira Cloud plan.
Usage of all 10 enforced Jira Cloud configuration limits per space, scheme, workflow and field, plus the 4 site guardrails. Colours follow the Radrly convention: green below 80%, yellow from 80% up to the limit, red above it.
Daily snapshots build a trend for each scope. LimitRadar forecasts the date a scope reaches 80% and 100% of its limit, with an interval, so you plan cleanup weeks ahead.
A ranked list of the scopes closest to a block, with the reason, the fastest fix and a check for bulk operations that Jira would reject in full.
Unused fields, options, work types, releases, components, grants, statuses, workflows, priorities and schemes, each with evidence: last used, screens, contexts, affected spaces and who created it.
Simulate a cleanup across every affected space and let LimitRadar suggest the smallest safe set of changes that brings a scope under your target.
Run a saved plan from the app with typed confirmation, fresh revalidation of each item, trash for fields, archive for releases, a pre-execution backup and undo wherever Jira allows it.
A reference scan checks filters, boards, dashboard gadgets, workflows, screens and contexts, and an imported Automation export, before an item can be marked Safe.
Track the temporary exemption after a Server or Data Center migration, find “(migrated)” duplicate fields and merge them safely, filling empty targets only.
CSV and Markdown for Confluence in Standard. Advanced adds a signed PDF limits report with an integrity hash chain and a Verify screen.
Two limits have been enforced since March 2026. Eight more are being switched on progressively since September 2026, on a date that varies per site. LimitRadar monitors all of them continuously, so you see the risk before the enforcement date reaches your site.
| Limit | Value | How it is counted |
|---|---|---|
| L1. Fields per space | 700 | Fields in the field schemes (or legacy field configuration schemes) associated with the space. Trashed fields do not count. |
| L2. Work types per space | 150 | Work types in the work type schemes associated with the space. |
| L3. Options per field | 20,000 | Options of a single field, across all its contexts. |
| L4. Work item security levels per space | 50 | Measured per work item security scheme and shown for every space that uses the scheme. |
| L5. Grants per permission | 50 | Grants of one permission in a permission scheme. |
| L6. Releases per space | 15,000 | Archived releases are not intended to count. LimitRadar also shows the count including archived releases. |
| L7. Workflows per workflow scheme | 150 | Distinct workflows in one workflow scheme. |
| L8. Statuses per workflow | 200 | Statuses in one workflow. |
| L9. Jira components per space | 10,000 | Jira components only. Compass components do not count. |
| L10. Priorities per space | 100 | Priorities in the priority scheme assigned to the space. |
Values as published by Atlassian on its data limits and guardrails page. LimitRadar ships this catalog inside the app and updates it with new app versions.
All write actions are off at install. A Jira administrator turns on write mode in Settings, and each action type has its own switch.
Locked, system and app-managed fields, default schemes and schemes in use are never offered for cleanup. Items without usage data are never marked Safe.
Map Jira groups to Viewer, Planner, Executor and Approver. When approval is on, a plan runs only after a different person approves its exact contents.
LimitRadar makes no calls outside Atlassian. No email, Slack or webhooks. Alerts appear in the app and, if you choose, as Jira work items in a space you pick.
Snapshots, forecasts, plans and the actions log live in Atlassian Forge hosted storage, following the data residency of your Jira site.
Granular read scopes for measurement and only the write scopes the cleanup actions need. Every request checks the signed-in admin's own Jira permissions.
Ask the LimitRadar agent in Rovo about your limits. It answers from LimitRadar data with real names, numbers and the snapshot time, and it can plan, simulate and run reversible cleanup in conversation after you confirm.
ConfigRadar answers what changed in your Jira configuration and who changed it. AccessRadar answers who has access and why. LimitRadar answers how much more fits, when you will hit the ceiling and what you can safely remove. MarginRadar covers cost, burn rate and margin from worklogs.
