Reports

Reports counts every SLA timer that stopped against the goal it was given: by SLA, person, priority, work type and period, with the detail of each one, saved views and exports.

The four readings

Each reading opens with one sentence that answers it, for example "75.0% of the SLA timers in this view met their goal, up 75.0 points on the 7 days before."

Choosing what to count

• Range. Read the moment each SLA timer stopped (Stopped, whether or not its request is resolved, so a first response met on a request still open counts), or the day the request was created (Created). The range reads, for example, "Stopped: Last 30 days · 30 Aug–28 Sep 2026". Presets: Last 7 days, Last 30 days, Last 90 days, Last 180 days, Last 365 days, This month, Last month, This quarter, Last quarter, or a custom range. Any range your history covers is read whole, and the same length of time before it is always read for comparison. Time in status reads the request's own resolution, so its range reads Resolved.
• Filters. Add filter offers SLA, Project, Priority, Assignee, Work type, Request type, Label, Organization, Component, Outcome, State and a JQL filter. Each filter narrows the count; Clear filters removes them.
• Group by up to three groupings: SLA, person, priority, work type, project, request type, Organization, component, label, goal tier, calendar, or any Jira field. The table nests them in the order you choose. With exactly two, Draw as a matrix.
• Over time by Automatic, Day, Week, Month, Quarter or Year. Days are counted in your site's time zone, and each chart says which zone.

When a filter leaves nothing, the page says how many SLA timers each filter took away, so you know which one to drop.

What Outcomes shows

• Tiles: Met rate, Breached, Median working time, Average working time, 90th percentile working time, Measured with no goal, and Reopen rate. Met rate, Breached, the median, the average and Reopen rate are read against the period before. When the reading holds an SLA timer whose goal is a date on the request and that date was empty when it stopped, a No date set tile and column count them apart, in no rate.
• Charts: met and breached over time, met rate over time, breached by SLA, and working time over time (median, average and 90th percentile). Show as table reads any chart as a table.
• Target line. When every SLA the report reads has the same Target met rate (one SLA chosen in the filters, say), the met rate chart draws it as a line. With different targets it draws none and says so: "These SLAs have different targets, so no single target line is drawn. Choose one SLA to see its target." In a table grouped by SLA, a row whose met rate is below its SLA's target reads Under target. It is a reading, not a problem.
• Custom chart: draw up to ten series in one chart, each counting what you choose (met rate, met, breached, measured, started, stopped, median working time) with its own filters.
• Compare with: draw a second reading beside this one, in the same chart and in one table, for example this quarter against last quarter.
• Where breaches concentrate: by status at breach, by person and by priority.
• The table: one row per combination of your groupings, with SLA timers, met, breached, measured, met rate, median, average, 90th percentile, reopened and reopen rate.

Every number opens the SLA timers behind it. A met rate counts SLA timers with a goal only; SLA timers measured with no goal are listed in their own column and in no rate. "None" means the request had no value for that grouping.

By person

• Group people by person, Jira group, or a team field.
• Tiles for the people with SLA timers, the SLA timers open now, and the ones breached, critical or at risk now.
• A chart of open SLA timers by person, and a table of each person's SLA timers in the range with met rate, median and 90th percentile, and the work they hold now. Requests nobody is assigned to are their own row.

SLA timer detail

• Show stopped SLA timers, or running ones.
• Layout: one row per SLA timer, or one row per request with a column per SLA.
• Each row names the request, the SLA, when it started, was due and stopped, how long it was paused, its working time, its goal, how far past the goal it went, and its outcome. Each row also says which definition it was measured under ("Measured under the definition of 1 Sep 2026"), and a deleted SLA reads "(deleted)": its history stays reportable.
• Columns: choose from the default columns and every Jira field, and Restore the default columns. The CSV always carries every chosen column.

Time in status

Working time and calendar time in each status, on requests resolved in the range: requests, visits, median and 90th percentile. Measure On each SLA's own calendar, or On one calendar you choose. A visit is one entry into a status, so a request that went back reads more visits than requests. A status no longer on the site still counts, under its id.

Saved views and links

• View: opens a saved view. A view holds its filters, its range, its groupings, its matrix, its series, its comparison, its columns and the zone its days are counted in.
• Save as a new view…, and Rename and Delete, each naming the view.
• Share: keep it to yourself, or share it with everyone who can open Reports, or with chosen groups and people, and name editors who can change it for everyone. A shared view always runs as whoever opens it, so nobody sees a request they cannot browse in Jira.
• The page address holds the reading, so a copied link opens what you see, and Back, Forward and a reload bring it back. An address that names only a range, such as /reports?range=last30, opens that range. In this release one grouping is not kept: Calendar. A view or a link opens without it, so choose it again on the page, and a schedule or a dashboard gadget of that view is not grouped by calendar.

Reading large ranges

A small reading answers at once. A large one runs in the background with a progress line; you can leave the page and come back, or stop it. The lines above the figures say how complete the reading is ("Complete. Every SLA timer that stopped in this range is counted, as the ledger had it at 14:31.") and, when something is still going on, what:

• Quartz is still reading this site's history, with how far it got.
• Row detail and medians cover a later month than the counts, when older detail was rolled up to save space: "Row detail and medians cover March 2026 onwards on this site; counts and rates cover the whole history."
• Some of the work waits for Jira's hourly limit for apps, why (Jira's limit was reached, this site has used its share of it, or Quartz is keeping the rest for more urgent work), and when reading goes on.

Reports does not name an SLA that is being recounted after a change; Radar and the SLAs page do, with how far the recount got. While a recount runs, Reports can show "This site's zone changed, so Quartz is putting its day buckets back in order." On Reports, that line means an SLA is being recounted.

A reading with a JQL filter is never counted without its filter. While the check of which requests match it waits for the same reasons, the page says so and when, for example "Quartz is holding back because this site has used its share of Jira's hourly limit for apps, so Quartz cannot check which requests you can open until 21:00. Run the search again after that to count your SLA timers.", and counts nothing until then. Time in status does the same.

Run the search again reads everything again, with your Jira access checked afresh.

Measured on a test site: Last 365 days over about 2,200 SLA timers, in a record of about 114,000, drew in about 24 seconds. A report over 100,000 real SLA timers has not been measured yet; see Limits and data retention.

Exports

Export offers:

Every drill has Export these rows. Report downloads are not recorded in the Audit log; the only downloads it records are those of the configuration file and of backups. Who can export: everyone who can view Reports, unless a Jira admin names who may on the Export reports grant; for anyone else the menu stays in place with every item unavailable and says "A Jira admin limits who can download reports."

Schedules and Report history

Open a saved view, then More > Schedule this view.

• A schedule runs the view daily (every day or chosen weekdays), weekly or monthly, at a time in your site's zone. A month that is too short runs on its last day.
• Recipients get a link, never the figures. Jira sends the message from a request the schedule names (Send it from this request), so Jira decides who really receives it, and Quartz asks Jira to leave out anybody who cannot browse that request. Send it even when nothing is counted is off by default.
• A schedule has no filters of its own: it runs the view, so changing the view changes what it sends.
• A view holds at most 3 schedules, and a site at most 50.

More > Report history lists every run of the view Quartz has made: when it ran, what it covered, the SLA timers rated, the met rate and the change against the previous run. Open a run to read it as it was on the day, or download it as CSV or Excel. A run does not change after it is made, and Quartz stores runs for as long as your SLA timer history setting; with For as long as the request exists, a run stays until someone removes it (a run of a deleted view can no longer be removed by hand).

On a Jira dashboard

More > Add to a dashboard places the Quartz SLA gadget on a Jira dashboard you choose, set to this view. The gadget runs the view as whoever looks at the dashboard. Without a view, the gadget shows Health (live), Success rate, Met vs Breached or Trend over time on the SLAs you choose. When it cannot check its figures just now because of Jira's hourly limit for apps, it says why and when to try again, and draws no figure. If Jira does not answer in time while Quartz adds the gadget, Quartz says it cannot tell whether the gadget was added; Add to a dashboard again looks for it on the dashboard first, and adds it only if it is not there.

Ask Quartz and the summary (Advanced edition)

• Ask Quartz: ask about these SLA timers in your own words (up to 300 characters). Quartz turns the question into filters you can see and change.
• Summary of this report: a few sentences on the numbers on the page.

Ask Quartz reads your question and the names of the SLAs, priorities, projects, work types and request types you can see on this site. The summary reads the totals on the page and the names of up to three rows with the most breaches: SLAs, people, or the values of whatever the report is grouped by. Neither reads a request's description or comments. See Limits and data retention for the AI allowance.

Questions

Why do Reports and Radar count differently? Radar counts SLA timers that are running now. Reports counts SLA timers that stopped in the range, by their outcome; running ones are counted apart ("Open now").

Why did a met rate change after the upgrade to Quartz 5? Quartz 5 applies extensions, JQL goal tiers and tier calendars on every screen, and counts an SLA with no goal as measured, not met. The release notes list the numbers that change after the upgrade, and why.

Why is a request I can see in Jira missing? Check the range field (Stopped or Created), the filters, and whether the request's SLA timer stopped in the range. An SLA timer with an exception is left out of every count.

Something unclear or wrong on this page? Contact support.