Best Screenshot Workflow for QA and Bug Reports

A bug report is a screenshot plus everything the screenshot does not say. Most of the back-and-forth on a ticket is a developer reconstructing context the reporter had on screen and did not capture.

This guide will cover what to capture (and what to record instead), annotation that survives review, stripping customer data before the image reaches a public tracker, and keeping evidence organised across a testing session.

See Explain for the annotate-and-attach loop, and the editor for non-destructive markup.

The full guide is being written. In the meantime the documentation above covers the same ground.