Breach Forecasting

Breach Forecasting highlights open issues that are likely to miss their SLA early — often before the live countdown turns red — so you can act while there is still time. Advanced

What it does

The Radar tells you what is breaching now or very soon. Forecasting looks further ahead: it highlights which open issues are likely to breach their SLA and surfaces them early, often before the live countdown shows any warning — so you can step in while there is still budget left. It applies to duration-based SLA goals (those measured in working time).

What you see

Each flagged issue shows four things, so you can prioritise at a glance: a risk band, a breach likelihood, a confidence level, and a short note summarising it.

Risk bands

Confidence

Confidence tells you how strongly to rely on a given forecast. Where Quartz cannot be sure, it says so rather than showing false precision — so a low-confidence flag is a hint to check, not a guarantee.

How to use it

Work the list top-down: start with Breaching and high-confidence High issues, since those have the least budget left, then move down the bands. Use Forecasting as an early-warning triage queue alongside the Radar — the Radar shows what is breaching now, Forecasting shows what is heading that way.

Your data stays in Atlassian

Forecasting runs entirely inside Atlassian on your own Jira data — there is no external service, no cross-customer model, and no data egress. Like every Quartz view, it is scoped to the issues you can already see in Jira, so a forecast only ever covers issues you could open yourself — see Permissions & data posture.

Forecast vs Radar

The two screens answer different questions and complement each other:

Was this page helpful?   Yes · No  ·  Contact support