Reports
Open a report, watch the replay synced to console + network + audio, mark its status, leave notes for your team.
When a customer submits a bug, your dashboard pings (Slack, in-app, or email — your team's choice). Click through and you land on the report-detail page.
The replay player
The center of the page. Synced playback of the rrweb DOM replay + microphone audio + drawing overlays. Use the timeline scrubber to jump around. The Console + Network tabs below the player are timeline-locked — clicking a network request jumps the replay to the moment it fired.
Status workflow
Reports start in New. As you work through them:
- Triaging — you've opened it, you're looking at it.
- Reproduced — you've confirmed the bug reproduces in your dev environment.
- Won't fix — known issue, intentional behavior, edge case you don't support.
- Fixed — fixed and deployed. The report becomes archive material.
Status is a single dropdown — pick the one that fits, save, move on.
Leave a note
Notes are for your team. The customer never sees them. Use them for:
- "Reproduced — same as INC-4218."
- "@dave — looks like a regression in the Apr 28 deploy."
- "User on iOS Safari, hits the same NetworkError as last week's reports."
Notes are markdown — links and code formatting work.
Dispatch
Slack dispatch happens automatically when the report finalizes — by the time you open the report, the message is already in the project's connected Slack channel. If a delivery failed (Slack token revoked, workspace removed), reconnect Slack from Settings → Integrations and the next report dispatches cleanly. Linear + GitHub dispatchers are on the near-term roadmap. See Dispatch.