The Radar
The Radar is your live landing screen — it counts open SLAs by status and shows a forward-looking board of what is about to breach next, scoped to the issues you can already see in Jira.
What the Radar shows
The Radar is the first screen under MONITOR and answers one question: what needs attention right now? It has two parts — a row of status counts and a "What breaches next" board that looks forward in time.
The counts summarise every open SLA goal in view: On track, At risk, Critical, and Breached. These statuses come from the same engine that powers the issue panel, recomputed on demand rather than read from a stored timer.
Every Radar scan runs as you, using your own Jira access. You only ever see issues you are allowed to browse — the Radar does not expose issues across projects you cannot otherwise open. See Permissions for the full data posture.
The "What breaches next" board
The board lists open, at-risk issues bucketed by how soon they will breach, sorted soonest first. The buckets are:
| Bucket | Meaning |
|---|---|
| Overdue | The goal has already passed its target — these are breaching now. |
| Next 8h | Will breach within the next eight business hours if nothing changes. |
| Next 24h | Will breach within the next day. |
| Next 48h | Will breach within the next two days. |
| All | Every open at-risk issue in view, regardless of bucket. |
The time-to-breach is pause-aware: an issue that is currently paused (for example, "waiting on customer") is measured against its remaining working time, so a paused clock is not counted down while the pause holds. The buckets reflect business hours from each SLA's calendar — nights, weekends, holidays and closed exceptions are skipped — so "next 8h" means eight working hours, not eight wall-clock hours.
Reading the buckets
Work top to bottom. The Overdue bucket is the cleanup list — these goals have already missed their target. The 8h and 24h buckets are where attention pays off most: these are the issues you can still save before the live countdown turns red. The 48h and All buckets give you a wider horizon for planning.
Each row shows the issue, its SLA goal and its status, so you can jump straight to the issue to act — for example to reassign it, or to extend the goal where that is justified (see the issue panel).
If a bucket is empty, nothing is forecast to breach in that window — that is the result you want. A growing 8h or 24h bucket is your early warning to redistribute work.
Scope and limits
The Radar scans open issues per SLA up to a limit and orders them by soonest breach. When that limit is reached, or when an issue's timing is too complex to evaluate fully in an aggregate scan, the Radar shows a warning so you know the view is truncated or that some pause time is counted approximately. In those cases the issue panel for an individual issue remains the exact source of truth, because it evaluates that issue's full timeline.
Muted goals are excluded from the Radar. Muting silences one SLA goal on one issue and removes it from breach counts and the board — it is an exception, not a fix, and every mute is recorded in the audit log.
Why is this at risk? Advanced
On the Advanced edition, a "✦ Explain risks" action explains the board in plain language — a short, readable summary of each at-risk row. It runs on Atlassian-hosted Claude inside the Forge runtime, so prompts never leave Atlassian.
On the Standard edition this action is locked. AI features are entirely part of the Advanced edition — see Editions.
Getting started from the Radar
For configurers, the Radar also hosts a first-run "Getting started" checklist. Its signals are computed from your real configuration, so each step ticks off as you complete it:
Create an SLA
Define your first goal — a target, a clock, and the issues it applies to. See Create an SLA.
Set up business hours
Add a custom calendar beyond the two seeded ones, or set a company holiday. See Calendars.
Map an SLA field
Write an SLA value back into a real Jira field to drive JQL and Automation. See SLA Fields.
The checklist is dismissible once you no longer need it.
Was this page helpful? Yes · No · Contact support