Skip to content
Toado Docs

Ticket detail

The ticket detail page is where the work happens. It puts the captured screenshot, the DevTools data, the comments, and the metadata in one place so you (or an AI agent) can debug end to end without leaving the page.

Layout

Two regions, roughly 80 / 20.

Main region (left, ~4/5 width)

  • The screenshot, with the annotation toolbar above it.
  • Drag-and-drop additional images onto this region to attach extras (mobile view, design ref, follow-up screenshot). Each attachment gets the same annotation tools.

Side region (right, ~1/5 width)

Top to bottom:

  • Title (editable inline).
  • Copy link button.
  • Status chips: column, resolved, branch (if started).
  • Created by with timestamp and avatar.
  • Assignees.
  • Description (editable, markdown).
  • Tabbed DevTools data viewer: Console, Network, Errors, Performance.
  • Comments chronologically below.

Resize the divider by dragging if you want a different ratio.

Editing the title

Click the title to edit inline. Enter to save, Escape to cancel.

The first time a ticket is created, the title is “Untitled capture”. A backend worker runs an AI title generator within a few seconds and replaces it with a descriptive title (e.g. “404 on /api/users in checkout flow”). You can edit the auto-generated title at any time.

The Copy link button at the top right of the side region copies a direct URL to this ticket. Useful for pasting into a Slack thread or referencing in an external tool.

Description

Markdown is supported (headings, lists, links, code blocks, inline code). Click to edit, Cmd+Enter to save, Escape to cancel. The description is what an AI agent reads via get_ticket, so detail here pays dividends.

DevTools panel

Four tabs that show the captured DevTools state:

  • Console: every captured console.* call with level (log, info, warn, error, debug), serialized arguments, timestamp, and stack trace.
  • Network: each request with method, URL, status, timing, headers, response size, and (where available) response body.
  • Errors: uncaught errors and unhandled promise rejections with stack traces.
  • Performance: navigation timing, long tasks, key Web Vitals (LCP, CLS, FID).

Each tab supports text-filter search. Filtering is local; it does not re-fetch from the server.

See DevTools panel for the full per-tab reference.

Comments

Chronological, oldest first. Each comment shows author, avatar, timestamp, and body (markdown).

Comments from MCP clients (e.g., Claude Code) are visually distinct. They have an MCP badge in violet and the author label includes both the user and the token name (e.g. “Jason (claude-code on macbook) · via MCP”). This makes audit trails self-explanatory.

Add a comment with the input at the bottom. Cmd + Enter to submit.

Mention a teammate with @. They get notified per their notification preferences. See Comments & mentions.

Metadata

FieldWhat it is
Source URLThe page the capture was taken from. Click to open in a new tab.
Created atThe capture timestamp.
Created by / reporterA workspace user for internal captures, or the reporter name/email supplied by an external reporter.
AssigneesUsers currently assigned to the ticket. Click to add or remove (if you have permission).
BranchGit branch the ticket is being worked on. Set by start_work_on_ticket from the MCP server, or manually.
ResolvedA flag independent of column position. A ticket can be resolved but still appear on the board until archived.

Widget and external reports

A source badge shows Widget, Report link, or Team snippet. Collected reporter name and email appear with the ticket metadata; custom-question answers are added to the ticket. External submissions are ready tickets, not private drafts.

Minimal widget reports can have only page and screenshot context. Standard reports can add Console, Errors, and passive Network evidence. Deep reports can add status codes and redacted request details. A missing or partial tab is not necessarily a failed submission, and DOM-rendered screenshots cannot reliably reproduce cross-origin iframes, video, WebGL, protected content, or some canvas elements.

Capture health banner

If any data category came back partial or empty, a non-blocking banner appears at the top of the screenshot region. Example:

Heads up: console capture unavailable on this page (CSP). Screenshot, network, and errors captured normally.

The banner is for both the human reader and any AI agent reading the ticket via MCP, so both know the capture is incomplete before debugging starts.

Keyboard shortcuts

ActionShortcut
Previous ticket in this project [
Next ticket in this project ]
Submit a comment Cmd + Enter
Save and return to source tab (after a fresh capture) Cmd + Enter
Open the shortcut cheatsheet ?
Close any modal or popover Esc

The save-and-return shortcut only fires when you reached the ticket via a fresh capture. Outside that flow it does nothing.

Full list: Reference › Keyboard shortcuts.

Where to next