features

Capturing a bug from the browser panel

Turning what is on screen into a task somebody can act on, without writing reproduction steps by hand.

Open the panel on the page where the problem is and capture. It takes the screenshot, the console output, the failing network requests and the page state together, and attaches them to a task.

Why capture rather than describe. Most of the time lost on a bug is spent reproducing it. A capture carries the console error and the failed request that a written report leaves out, because the person writing the report could not see them either.

Choose what to keep. Captures are attached to a task only when you save them. A capture you discard is never uploaded.

Sensitive pages. A capture includes what was on screen, which may include customer data. Check before attaching one to a task a seller can read.