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 Communications → Tickets → (your bug board). If you signed up in English, that board is called Bugs and it starts with the columns Open, In Progress, To Test and Done. A board you made yourself starts with a single column called New.
Reports arrive in the first column. Each card shows the ticket's title, any labels on it as coloured chips, a preview of the description, a priority badge, the date and the logo of the widget it came from. Unread tickets carry a dot, and the board's row in the sidebar carries a count.
Reading a bug ticket
Click a ticket to open the detail panel. Down the right-hand side, the Actions list opens whatever the report carried:
- View screenshot — the image the visitor marked up, full size in a new tab.
- View recording — the short screen recording, if they made one.
- View replay — the session replay of the browsing that led up to the report, if session replay is on for that widget.
- Event log — what happened in the page, including console errors and network requests.
- Metadata — browser and version, operating system, screen and window size, the page address, the visitor's language and how long their session had been running. Values your code set with
Yaplet.setTicketAttribute()appear with the ticket's other answers rather than here. - View chat — opens the visitor's conversation, when there is one.
Move tickets through your workflow
Drag a ticket from column to column as work progresses. A typical bug board runs:
- Open — unreviewed, just arrived.
- In Progress — a developer has confirmed the bug and is on it.
- To Test — the fix is written and needs checking.
- Done — finished.
Each column header's three-dot menu renames it, changes its colour, moves it left or right, archives or deletes every ticket in it, or deletes the column. Add Column at the top right adds more, up to a generous per-board ceiling you are unlikely to reach. Match your team's real process rather than ours.
Assign, prioritise and label
From the detail panel, assign the ticket to a teammate and set its priority to Low, Medium or High. Labels are the third axis: short coloured tags that say what a ticket is about rather than what stage it is at, so billing and mobile can sit on the same card. Filter the board by any of these from the Filters button above the columns — picking two labels shows only tickets carrying both.
Get a ticket out of Yaplet
Two entries in the same Actions list hand a bug to someone who does not use Yaplet:
- Copy for AI puts the ticket on your clipboard as readable text, ready to paste into ChatGPT or any other assistant. It never includes customer details or technical logs, whatever the export options allow — it is deliberately the safe, compact version.
- Export ticket… downloads a file, and lets you choose the format and whether to include the logs.
For the formats and what each is good for, see Moving boards in and out of Yaplet.
Add internal comments
Use the comment field on the ticket to leave notes for your team — reproduction steps, links to commits, context that did not fit in the original report. Comments are internal; the visitor never sees them.
Everything on this screen happens on the server, so a colleague with the same board open sees your change immediately and the mobile app stays in step. Ticket deletions are recorded in your audit log.
How boards work
For a full overview — column types, visibility, forms, labels and what deleting a board destroys — see Boards — the kanban primitive behind tickets, bugs, and feature requests.