Cookies on this site

With your OK we use Google Analytics and Google Ads cookies to see which pages and ads bring people here. Nothing loads unless you accept. Privacy policy The LimitRadar app is not affected and still sends no data outside Atlassian.

Privacy policyChange it any time in Cookie settings at the bottom of the page.

Radrly
LimitRadar
Try it free

What is LimitRadar?

LimitRadar by Radrly is a Jira Cloud app (Atlassian Forge) that forecasts and monitors Jira configuration limits (custom fields, workflows, statuses, schemes) per site and space, and helps clean up unused configuration safely with a simulator and undo.

Updated 12 November 2026.

Who it is for

LimitRadar for Jira is for Jira Cloud administrators on growing sites: sites where fields, work types, workflows and statuses are added faster than they are removed, and sites that have just migrated from Server or Data Center. It works on every Jira Cloud plan, with the interface in 12 languages (English, German, Japanese, French, Spanish, Brazilian Portuguese, Polish, Korean, Italian, Dutch, Simplified Chinese, Traditional Chinese).

The problem it solves

Jira Cloud enforces configuration limits. Fields per space (700) and work types per space (150) have been enforced since March 2026, and eight more are rolling out since September 2026. Above a limit, Jira refuses to add more, and a bulk action that would exceed it is rejected in full. The native Site optimizer is on Premium and Enterprise; elsewhere admins count with scripts and spreadsheets, and find the limit on the day someone needs one more field. See the full list of Jira Cloud limits.

How it works

  1. Measure. After install, LimitRadar scans the site and counts every space, scheme, workflow and field against the 10 enforced limits and the 4 guardrails. It takes a snapshot every day and is read only at install.
  2. Forecast. A Theil-Sen trend line on the daily counts gives the date each scope is expected to reach its limit. With at least 28 days of data, the forecast can include a weekly pattern, labelled Weekly pattern included. Next to block ranks the scopes that will block first, and What if I add tells you whether Jira would accept a planned bulk add.
  3. Find cleanup candidates. Unused fields, options, statuses and schemes are listed with a safety level, the reason and the references found. Labels, filters, field options, work types, statuses, priorities and security levels also appear as proposals with evidence; LimitRadar does not delete them and they cannot enter a plan. On Cleanup, Filters also flags saved filters whose JQL names custom fields that no longer exist, with the missing field ids as evidence; this is review only and never deletes or writes the filters. The scan reads which saved filter a dashboard gadget uses, so those filters stay at Review. Labels Jira knows that no work item carries appear as proposals only: no merge, no delete and no undo.
  4. Simulate and clean up. The simulator shows the effect on each limit first. A plan keeps a backup, and each action needs write mode switched on by a Jira admin and typed confirmation. Undo works wherever Jira allows it.
  5. Report. Export the limits report as CSV or Markdown, and read the weekly digest in the app. When an alert space is set, admins can pick the work type for alert and approval work items; those items get limitradar labels and a Kind line that Jira Automation can match. Advanced adds threshold alerts after each scan and a signed PDF limits report.

What makes it different

  • It covers all 10 enforced limits and the 4 guardrails on every Jira Cloud plan, from a catalog that ships inside the app with each Atlassian source.
  • It never shows an invented zero. A limit it could not read is marked as not available or not counted.
  • It reads new field schemes or legacy field configuration schemes, whichever your site uses, and shows the count without locked fields next to the total.
  • It runs on Atlassian. LimitRadar is built on Forge with granular scopes only, stores data in Forge storage on your site and makes no calls outside Atlassian. See Security.
  • Advanced adds a Rovo agent with 33 actions and 10 read-only MCP tools for AI clients, which stay off until a site admin enables them. The interface is in 12 languages (English, German, Japanese, French, Spanish, Brazilian Portuguese, Polish, Korean, Italian, Dutch, Simplified Chinese, Traditional Chinese), taken from the Jira user's language.

Where to install it

Install LimitRadar from its Atlassian Marketplace listing, which also shows the Standard and Advanced editions. The documentation covers the first scan.

Who makes it

LimitRadar is made and supported by Radrly (Radrly Sp. z o.o., Poland), which builds Atlassian Forge apps for Jira Cloud, including AccessRadar, ConfigRadar, CapRadar, LeakRadar and MarginRadar.

FAQ

Is LimitRadar a risk or exposure-limits platform?

No. LimitRadar is a Jira Cloud admin app for configuration limits, such as fields per space, options per field, workflows and statuses. It does not deal with financial risk or exposure limits.

Which Jira Cloud limits does LimitRadar track?

All 10 enforced Jira Cloud configuration limits, from fields per space and work types per space to statuses per workflow and priorities per space, plus the 4 site guardrails. The full list with values is in the Jira Cloud limits guide.

Can I undo a cleanup?

Yes, wherever Jira allows it. Trashed custom fields can be restored from the Jira trash within 60 days, and removing a field from a scheme, a role actor or a grant can be undone from the Actions log. Deleting an option or a status has no undo, because Jira recreates it with a new ID.

More Radrly apps for Jira