Cookies on this site

We use Google Analytics and Ads cookies only with your OK. 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

LimitRadar for Jira Cloud

See which Jira Cloud limit you will hit next

LimitRadar counts all 10 enforced configuration limits and 4 guardrails across every space, ranks the scopes closest to a block and forecasts when each one fills up.

30-day free trial. Standard is free for up to 10 users. Runs on Atlassian, zero egress.

LimitRadar Overview in Jira admin settings: KPI tiles for blocked now, at or above 90%, warning scopes and next block, above a card for every enforced limit.
  • 69 / 700 fields per space
  • 6 / 150 work types per space
Every Jira Cloud limit with its highest scope and the next block, in LimitRadar.

Next to block, worked through

An example site after 14 daily snapshots. Next to block ranks the scopes closest to a limit, with the forecast for each one.

1. Fields per space

MOBILE space, limit 700

  • Used658 of 700 (94%)
  • Left42 fields
  • Trend, last 14 days+0.5 a day
  • Forecastfull in about 84 days

2. Statuses per workflow

Support workflow, limit 200

  • Used168 of 200 (84%)
  • Left32 statuses
  • Trend, last 14 days+0.25 a day
  • Forecastfull in about 128 days

3. Work types per space

OPS space, limit 150

  • Used121 of 150 (81%)
  • Left29 work types
  • Trend, last 14 daysflat
  • Forecastno date on a flat trend

What if I add 50 fields to MOBILE? 658 + 50 = 708, which is 8 over 700. Jira rejects a bulk add like that in full, and What if I add tells you before you try.

The 10 limits and 4 guardrails it counts

  • 700fields per space
  • 150work types per space
  • 20,000options per field
  • 50work item security levels per space
  • 50grants per permission
  • 15,000releases per space
  • 150workflows per workflow scheme
  • 200statuses per workflow
  • 10,000Jira components per space
  • 100priorities per space

Plus 4 site guardrails that Atlassian recommends: work items per site, spaces per site, space role actors per space and space roles per user. Values as published by Atlassian, explained in Jira Cloud limits: all 10 configuration limits and 4 guardrails.

What you get

Advancedmarks features in the Advanced edition. Everything unmarked is in both editions.

  • Usage

    Every limit, every scope

    Usage of all 10 enforced limits per space, scheme, workflow and field, plus the 4 site guardrails, measured with each daily snapshot.

  • Forecast

    A date only when the data supports one

    A forecast date from 14 daily points, an early estimate from 7 to 13, and no date below 7 points or on a flat trend.

  • Next to block

    What Jira blocks next, and why

    A ranked list of the scopes closest to a block, with the reason, the fastest fix and a What if I add check before a bulk change.

  • Cleanup

    Clean up with evidence and undo

    Cleanup candidates with evidence, a simulator, typed confirmation and undo wherever Jira allows it. Read-only until a Jira admin turns on write mode.

  • Alerts

    Threshold alerts after each scan Advanced

    Configurable thresholds, with alerts that can open Jira work items in a space you choose. Standard has a weekly digest with fixed 80 and 90 percent thresholds.

  • Reports

    Signed PDF limits report Advanced

    A PDF report with a SHA-256 hash chained to the previous report, and Verify. Both editions export CSV and Markdown.

How it works

  1. Install LimitRadar from Atlassian Marketplace. It works for Jira administrators, on every Jira Cloud plan.
  2. Run the first scan. The Overview shows each limit with its highest scope, a colour band and the enforcement status as Atlassian publishes it.
  3. Let the daily snapshots build a trend. After 7 days you see an early estimate, after 14 a forecast date.
  4. Open Next to block to see which scope fills up first and the fastest fix.
  5. Clean up safely with the simulator, a backup before every run and undo wherever Jira allows it.
LimitRadar for Jira: Cleanup page with the Write mode is off notice and a list of field candidates, each with a Do not touch safety label and its reasons.
Cleanup candidates with evidence. Nothing changes until write mode is on.

Most sites hit fields first. Read 700 fields per space in Jira Cloud: count, compare, forecast.

Frequently asked questions

Which Jira Cloud limits does LimitRadar track?

All 10 enforced configuration limits: fields per space, work types per space, options per field, work item security levels per space, grants per permission, releases per space, workflows per workflow scheme, statuses per workflow, Jira components per space and priorities per space, plus the 4 site guardrails.

How is the forecast made?

A daily snapshot builds a trend for each scope. LimitRadar gives a forecast date from 14 daily points, an early estimate from 7 to 13 points, and no date at all below 7 points or on a flat trend.

Does LimitRadar change my configuration on its own?

No. It is read-only at install. Cleanup needs write mode switched on by a Jira admin, and every run shows the plan, the simulated effect and the undo path first.

Does any data leave Atlassian?

No. LimitRadar runs on Atlassian Forge with zero egress. Snapshots, forecasts and the actions log live in Forge hosted storage under your site’s data residency.

Which languages does the interface support?

The interface is available in 12 languages (English, German, Japanese, French, Spanish, Brazilian Portuguese, Polish, Korean, Italian, Dutch, Simplified Chinese, Traditional Chinese).

Find your next limit before Jira does

Install from Atlassian Marketplace and run the first scan. The forecast builds itself from daily snapshots.

30-day free trial. Standard is free for up to 10 users. Runs on Atlassian, zero egress.

LimitRadar is made by Radrly (Radrly Sp. z o.o.), which also builds MarginRadar, AccessRadar, ConfigRadar, CapRadar and LeakRadar for Jira Cloud.

More Radrly apps for Jira