The bug detail page: a guided tour

Open any bug from a board and you land on its detail page, the single place where everything captured about that issue lives. It can look busy at first, so this tour walks you through each area and shows where to find it.

Across the top sits the bug's title and its controls. Change the Status (from Open through In Progress, Dev Testing, QA Testing, to Closed or Reopened), set a Priority from Critical to None, add Labels, and pick an Assignee. The assignee control is the same whether you hand the bug to a teammate or to an AI agent.

The main panel opens on the Instant Replay, a reconstructed DOM recording of the moments before capture, not a video. Press play or drag the scrubber to step through exactly what the reporter did. Because it rebuilds real page structure, it stays sharp at any zoom. See Watching a session replay for the player controls.

Below the replay are tabs. The Console tab lists log, warn, and error messages with stack traces; the Network tab lists each request with its method, URL, status, timing, and masked headers (bodies are never captured). Both are synced to the replay timeline: scrub to the failure and the culprit error and request light up together. Dig deeper in Reading console logs and Inspecting network requests.

The Environment tab answers "on what?" It shows the page URL, operating system, browser and version, viewport size, and screen resolution captured at the moment of the report. This is often enough to spot a bug that only appears on one browser or a small screen.

The sidebar keeps the human context. The Activity feed is an automatic, time-stamped log of every change: status moves, reassignments, label edits, and integration events like a linked GitHub pull request. The Comments thread is where your team (and assigned agents) discuss the fix, ask questions, and leave notes.