The report page
Opening a report from the inbox puts the capture and the controls that act on it on one screen: the evidence on the left, the triage panel on the right. A report is meant to be actionable the moment you land on it, with nothing to export first.
Not everything a report carries is drawn here. Attached files and screen recordings are reached from the project’s Gallery tab — and only older reports have them at all, because no capture surface sends either any more. And a rating, which the REST API accepts and stores on a report, is shown on no dashboard screen; read it back through the API.
The top bar and the title
Section titled “The top bar and the title”- A back link to the inbox and, when you arrived from a list of several reports, your position in it with previous / next arrows. The j and k keys do the same, so you can work a backlog without returning to the list between reports.
- The title: the short name if one has been accepted, otherwise the first sixty characters of what the visitor wrote. Beside it, the status badge and, when the report carries marks, a badge counting its pins.
- The capture mode badge, Normal mode or Technical mode: the mode the project was in when the report was filed, which is what decides what the report carries. A report filed before capture modes existed shows no badge.
The evidence (left column)
Section titled “The evidence (left column)”The screenshot and its marks
Section titled “The screenshot and its marks”The screenshot renders with every mark replayed over it: outlined elements, orange margin bands, and numbered pins. Beside the canvas each mark also gets a row, showing its note — or, when it carries none, what kind of mark it is and, for a margin band, which side it sits on.
Each pin carries its own note, its own discussion thread (reply to it, @mention a teammate inside it, edit or delete your own replies), and its own resolve toggle. That is the Figma metaphor: a conversation attached to the spot it is about, closed one spot at a time, rather than one thread for the whole page. The resolve toggle and the reply box are drawn for a full triage seat — see the permissions note under the triage panel.
Technical context
Section titled “Technical context”One card, with only the sections the report actually carries. What it carries follows the report’s capture mode.
A Normal-mode report has no technical sections. The card says so in one sentence — Filed in Normal mode: the screenshot, notes, page and device only. No console, network, errors or performance were recorded. — so “nothing was recorded” never looks like “nothing went wrong”. The device is still there.
A Technical-mode report shows the sections it has:
- Console: the captured console output, each line prefixed with its level.
- Network: the failed requests, each as its status, method and URL. When nothing failed, the section says that every request the page made succeeded, rather than disappearing.
- Technical capture: every request the page made as a table (status, method, URL, type, duration, size; with a filter for only failed and slow ones), exceptions with their stack traces and repeat counts, the browser’s own messages (Chrome/Edge extension only), Performance figures, and the Environment and Connection details.
- Steps before sending: the breadcrumbs — the recent clicks and page or route changes that led to the report, oldest first.
- Device: browser, viewport, language and the rest, as a named list. The user agent is rendered readably rather than as its raw string, and a field that is genuinely empty is left out rather than shown as a blank row.
A report filed before capture modes existed displays as it always did. If a report carries none of these, the card says so plainly instead of rendering empty headings.
How big this is
Section titled “How big this is”When the report is part of a group, a strip under the title states it in numbers: how many reports are in the group — this one plus everything merged into it — how many distinct people that is, how many of them were anonymous, and when it was first seen.
Two figures are kept apart on purpose. Merged reports are what your team has decided; a suggested group is what a model has proposed and nobody has confirmed. When something has been proposed, the strip says so and offers to merge them all at once. That offer is drawn from the proposal sitting on the report rather than from your plan, so it stays put on reports proposed before an account moved off AI; the Merge them all button beside it needs a full triage seat. See AI triage.
Internal discussion
Section titled “Internal discussion”The team-only comment thread sits in the left column, next to the evidence it is about. It is never shown to the reporter. See Comments & @mentions.
The triage panel (right column)
Section titled “The triage panel (right column)”The Triage card holds four controls, each saving the moment you change it:
- Status:
new,in_progress,waiting,resolved,archived. - Priority:
none,low,medium,high,urgent. - Assignee: exactly one teammate, or unassigned. The list only offers people who can actually reach this report’s project, so it never offers a name the next request would refuse.
- Labels: tick any of the space’s labels.
When a model has proposed a triage, its proposal sits above these four inside the same card, drawn dashed so it reads as provisional; accepting it writes the priority and adds the suggested label.
All four are covered in Labels, priority & assignment and Status lifecycle. Changes are recorded with who made them and when, in the platform audit trail. That trail has no reader in the dashboard, so if you need the record, ask support for it.
Below it, and only when each one applies:
| Card | When it appears | What it does |
|---|---|---|
| Ticket | Once an issue is linked, always; before that, for a full triage seat | Creates the issue in your connected tracker or, with nothing connected, points you at where to connect one instead of making you press a button to find out. Once linked, it shows the issue key and opens it. |
| Changelog | The report is resolved, belongs to a project, your plan includes announcements, and you hold the permission to create content |
Turns the fix into a changelog draft, so the person who reported it hears back. See Close the loop. |
| Custom fields | The space defines any | Your own fields (text, number, switch or select) on this report. A value from a retired option is offered back rather than silently blanked. |
| Duplicate | Always | Link this report to the one it duplicates by id, or unlink it. Reports merged into this one are listed by name, each with its own unlink, so a merge made by mistake is reversible by whoever notices. |
| Report details | Always | The reporter, the page URL, and the reporter’s full comment. |
A triager with the delete permission can also delete the report outright, which is the answer to a visitor asking for their own report to be erased.
AI analysis and what automations did
Section titled “AI analysis and what automations did”When automations are on your plan and AI is switched on for the account, two more blocks appear on a report:
- AI analysis: what the model read in this report, shown as facts rather than a suggestion — category, severity, area and sentiment, a probable cause when the report carries console or network evidence, and a ticket ready for a developer: steps to reproduce, expected and actual. A report the model never read (it arrived before consent, or credits ran out) simply has no card.
- Done by automations: a timeline of every change a rule made to this report, each with the rule’s name, the AI confidence and the reason. Every change that can be reversed has an Undo that puts the previous value back; if someone has changed that value since, Undo refuses and says so instead of overwriting a person’s decision. Actions that sent something out (a ticket, a channel post, an email) are listed but cannot be undone.