The platform-side destination for in-app reports. Filters by status, product area and client; screenshots open in a lightbox you can step through with arrow keys; each ticket carries a human-pasteable code, the auto-captured page, dialog and URL, and — when resolved — a required summary, an optional rationale and test steps. Exports pair each description with its own screenshots as Markdown.
Also called: bug queue · report inbox · where reports go · ticket list
- 1Reports arrive with their ticket code (L2B-XXXXXX) already assigned; screenshots are archived into the org's media library under 'L2B Bug Reports / <year> / <month, area>' with cloud storage as a fallback
- 2Resolving requires a summary — the server rejects a resolve without one, so a 'Resolved' badge can always answer what was fixed
- 3Dismissing requires a reason; reopening clears the close stamps and increments a reopen counter
- 4A stable problem fingerprint assigned at resolution flags a second report of the same problem as a recurrence
Reports arriving by email, text and phone call meant nobody could say how long anything took, or notice that three accounts had reported the same thing. Every report from every account now lands in one queue with its ticket code, its screenshots and the screen it was captured on, and closing one requires writing down what changed and why — which is the answer to 'what did we actually tell this client' when they reply a week later confused. Every close and every rejection is timestamped, so time to resolve is a number instead of an impression.
- Reports closed with no record of what was done
- Recurring problems treated as brand-new every time
- No measurable time-to-fix
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 →