Your bug board is the kanban workspace where every incoming bug report becomes a ticket ready for your team to act on. This article covers how to read, prioritise, assign, and resolve bug tickets efficiently.
Where bug tickets land
From the sidebar, open Tickets → [your bug board]. New reports appear in the first column — typically named Open for boards created during widget setup, or New for manually-created boards. Each card shows the form name (or a custom title if you've set one), a short preview of the visitor's description, a priority badge, the submission date, and the widget logo.
Reading a bug ticket
Click any ticket to open the detail panel. You'll find:
- Screenshot — annotated image the visitor submitted. Click to open the full-size lightbox.
- Session replay — play button to watch a replay of the visitor's session leading up to the report. Available when session replay is enabled on the widget.
- Console logs — browser errors and warnings from the session.
- Network logs — HTTP requests with timing.
- Device and browser info — OS, browser version, screen size, pixel ratio, URL, language.
- Custom metadata — any application state your SDK pushed (user ID, plan, experiment variant, etc.).
- Linked conversation — click through to the visitor's chat history if they have one.
Move tickets through your workflow
Drag a ticket from column to column as work progresses. A typical bug board workflow:
- New — unreviewed, just arrived.
- Reproduced / In progress — a developer has confirmed the bug and is working on it.
- Fixed — the fix is deployed.
- Won't fix — acknowledged but not in scope.
You can rename, reorder, recolor, or toggle visibility on any column from its three-dot menu on the board view; use Add Column at the top of the board to add new ones — match your team's actual process.
Assign and set priority
From the ticket detail panel, assign the ticket to a specific agent or developer using the Assignee dropdown. Set priority to Low, Medium, or High. Use the board's Assignee filter to show only the tickets assigned to one agent.
Add internal comments
Use the comment field in the ticket to leave notes for your team — reproduction steps, links to commits, context that didn't fit in the original report. Comments are internal: the visitor never sees them.
How boards work
For a full overview of the boards data model — column types, visibility, forms, and ticket structure — see Boards — the kanban primitive behind tickets, bugs, and feature requests.