Work the board, hunt in the list
When you are moving work forward, the board is the faster surface: status changes are a drag. When you are looking for one thing, switch to the list and filter.
The inbox is where every captured report lands. It has two views of the same set of reports: a board you drag work across, and a list you filter and read densely. Both are scoped to your account, to your active space, and to the projects you can reach.
Open it from the sidebar. The board is the default view; the Board / List switch in the header moves between the two.
| View | Path | What it is for |
|---|---|---|
| Board | /s/{space}/feedback |
Managing flow. One column per status, drag to move and reorder. |
| List | /s/{space}/feedback/list |
Hunting and filtering. A dense table with filters, search and bulk actions. |
Three capture surfaces write reports: the <script> snippet on your site, the browser extension
your testers use, and, on plans that can mint an API key, the
REST API. One more route into the inbox is not capture at all — opening
a survey response as a report, from that survey’s results page.
Every report is created with status new, and there is nothing to “receive”. It is in the list
the moment it is stored. On the board it takes its place in the new column, which orders by
where cards have been dragged to, then by priority, then by recency — so on a column that is already
drawing its hundred cards, a report that has just arrived with no priority yet can sit below the cut
until you prioritise it or go find it in the list.
A report also carries a source — one of extension, public, survey or api — which no
screen prints as such. What the report page prints is a Reporter, derived from it: the tester’s
name for an extension report, and for a public one the visitor’s email, or Public visitor when
they gave none. A survey- or API-created report has nobody attached to it, so its reporter line reads
unknown.
The board has one column per status, each in its own colour, with the count of reports in that status beside its name. That count is not cut down to the hundred cards the column draws — but on Free it counts only inside the plan’s history window, exactly as the cards do, and the line above the board says how many older reports are outside it. See Your plan’s history window below.
Drag a card to reorder it inside its column, or across to another column. A cross-column drop changes the report’s status and notifies whoever the change concerns, exactly as changing the status on the report page would.
A card shows, top to bottom: the screenshot thumbnail, up to three labels and a +N chip for any
beyond them, the report’s title if one has been accepted, the first 120 characters of the visitor’s
own words, then any machine proposals for triage, duplicate or title — on plans that include the
AI copilot — and finally a footer with the priority (only when it is not
none), the project, a N similar chip when the nightly pass has grouped other reports under this
one, markers for a screenshot, for attachments and for comments, how long ago it arrived, and the
assignee’s face.
The thumbnail is a second, smaller file, made by a background job just after a report that has a screenshot lands. So a card draws without a cover in two different situations: the report never had a screenshot at all, or it has one and the job has not run yet. The footer’s screenshot marker is the honest one, and tells the two apart: it says there is a picture whether or not the thumbnail has been made.
One row per report, deliberately compact. Left to right:
| Column | What it shows |
|---|---|
| (select) | A checkbox to include the row in a bulk action. Selecting the whole page is a labelled Select all checkbox in the bar above the table, not a box in this header. |
| Comment | The accepted title when there is one, then the reporter’s own words (first 70 characters), then the report’s labels as coloured pills. |
| Project | The project the report belongs to. |
| Status | New, In progress, Waiting, Resolved or Archived as a status badge. |
| Priority | A word, not a colour alone: Urgent, High, Medium, Low, None. |
| Assignee | The teammate who owns it, with their avatar, or Unassigned. |
Clicking anywhere in a row except the checkbox opens the report. The list paginates at 20 reports per page.
From an open report you can keep going without returning to the list: the arrows in the report’s top bar, along with the j and k keys, step to the next and previous report.
Be aware of what they step through. The queue is the inbox’s own — the 100 most recent reports,
newest first — and not the filters, sort, saved view or board column you arrived through. It is taken
once, when you open a report from the list, and then carried unchanged for the whole walk, so
anything filed while you are working through it will not appear until you go back. The 3 / 100
counter beside the arrows counts that queue, not the set you were looking at. If you are working a
filtered set, expect the arrows to walk out of it.
The filter bar sits above the list. On a phone it is collapsed behind a Filters button that carries a count, so an active filter is never hidden silently.
Status: any status, or one of new, in_progress, waiting, resolved, archived.
Priority: any priority, or one of none, low, medium, high, urgent.
Project: one project, or all of them.
Assignee: anyone, or one teammate.
Label: one label; only reports carrying it are shown. This one appears only once the account has at least one label defined — until then the bar carries five controls, not six.
Search: free text.
Filters combine, and the list reloads as you change them; there is no Apply button. They are not kept in the address bar, so a filtered view is not a shareable link; to share one, save it as a view.
Work the board, hunt in the list
When you are moving work forward, the board is the faster surface: status changes are a drag. When you are looking for one thing, switch to the list and filter.
Filter to yourself
Set Assignee to your own name to see only what you own. The board footer’s avatars do the same job at a glance.
Label, then filter by label
Bulk-apply a label to a run of related reports, then use the Label filter to pull that set back up whenever you need it. See Labels, priority & assignment.
Save the filters you use daily
A saved view is shared with everyone in the space, so “untriaged, urgent” is one click for the whole team rather than the same filters set by hand each morning.