Get started
Quartz tracks SLAs on any Jira project and runs entirely on Atlassian — no external server, no data egress. This guide takes you from install to your first live SLA in about ten minutes.
You need Jira administrator (or project admin) rights to configure SLAs, and Quartz installed from the Atlassian Marketplace. Works on Jira Software, Work Management and Service Management — not just JSM.
What is Quartz
Quartz measures how long issues take against the targets you set — first response, resolution, or any custom goal — using business calendars so the clock only runs during working hours. It shows live status on every issue, surfaces what is about to breach on the Radar, and proves your service levels with reports and an audit trail.
SLA status is computed on demand, so there is nothing to backfill — install it today and historical issues report correctly straight away.
Step-by-step quick start
Create a business calendar
A calendar defines your working hours, time zone and holidays. The SLA clock pauses outside these hours. Quartz ships with a default 9–5 Mon–Fri calendar you can clone.
Open Quartz → Calendars → New calendar, set your hours and add holidays.
Define your first SLA
An SLA is a goal (e.g. Resolution) plus targets per priority or JQL. Open Quartz → SLAs → New SLA and choose what starts, pauses and stops the clock.
| Priority | Target | Calendar |
|---|---|---|
| Highest | 4h | 24×7 |
| High | 1 business day | Business hours |
| Medium / Low | 3 business days | Business hours |
Scope the SLA to the right work with JQL, for example:
project = SUP AND type = Incident AND status != DoneSee SLA status on issues
Open any matching issue — the Quartz panel shows time remaining, the target, and a colour-coded status spine (on track / at risk / breached), pause-aware.
Open the Radar
The Radar buckets every open issue by time-to-breach, so you act before SLAs are missed. On the Advanced edition, Breach Forecasting flags which open issues are likely to miss, early.
Want SLA deadlines on the issue itself or in Automation rules? Quartz can mirror remaining time, status and breach counts into real Jira fields — see Write SLA data to Jira fields. No outbound webhooks, no external server.
Standard vs Advanced
All SLA tracking, calendars, the Radar and reports are in Standard. Advanced adds the predictive and AI layer — all of it on Atlassian-hosted Claude, so prompts never leave Atlassian.
| Capability | Standard | Advanced |
|---|---|---|
| SLA timers, calendars, Radar, reports, CSV | ✓ | ✓ |
| Write SLA data to Jira fields & Automation | ✓ | ✓ |
| Breach Forecasting | — | ✓ |
| AI report summaries, “why at risk”, NL queries, Rovo agent | — | ✓ |
Quartz uses read-only scopes and Atlassian storage. There is no external backend and no data egress — exports run in your browser, and AI features use Atlassian-hosted Claude. See Security & data residency.
What's next
Was this page helpful? Yes · No · Contact support