The aggregate view of the bug corpus. It reads one pre-computed payload; the browser never sees the raw reports. Range presets run from seven days to all time with a custom range, and breakdowns cover reported versus resolved versus rejected, backlog, hour-of-day and day-of-week patterns.
Also called: bug trends · how fast do they fix things · quality metrics · recurring problems · bug metrics · quality dashboard · time to fix · recurring bugs
- 1Everything is computed server-side; the client only formats.
- 2Each average renders with its sample size.
- 3A metric that cannot be computed shows an em dash rather than zero.
- 4Series and breakdowns use one consistent colour ramp led by the brand accent.
- 5The whole corpus is queried by range, including all-time.
The component states its honesty rule: 'Every average is shown WITH its sample size, and any metric that can't be computed from the data on hand renders "—" rather than 0 — a fabricated zero in a quality dashboard is worse than an honest blank.'
- Fix speed was anecdotal.
- A zero on a quality dashboard was indistinguishable from missing data.
- Recurring problem areas were not visible in aggregate.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →