What a good bug screenshot shows
- Enough context to find it: the page or window, not just the broken button.
- What went wrong, marked: a box or an arrow on the problem, so nobody has to hunt.
- The order of things: numbered steps when it takes more than one click.
- Nothing private: customer data and keys blurred.
Step by step
- Capture the window rather than the whole screen, so the report shows where the bug lives without your other tabs.
- Point at it. A rectangle around the problem, an arrow from a label, or a short Text note (“should say 3 items”).
- Number the steps. The Numbered steps tool drops 1, 2, 3 where you clicked.
- Copy the error text. Copy text on the error message gives you text to paste under the image.
- Blur what’s private. Auto-redact catches emails, card numbers and keys.
- Paste it into the ticket. The capture is already on your clipboard; drag the Copied card into the tracker, or save it with a smart file name like
checkout-typeerror.png.
When one picture isn’t enough
- A long page or log: a scrolling screenshot.
- Something that flickers or happens over a few seconds: Burst grabs the frames, and you can attach a GIF.
- A menu that closes when you press a key: capture after a delay from the tray.
Questions
Should I paste the error as an image or as text?
Both. The screenshot shows where it happened; the text can be searched and copied into a fix. Copy text gets you the text from the same capture.
Can AI write the bug report for me?
Glintshot’s Ask has a Bug report question that drafts steps, what happened and what was expected from the screenshot. Read it before you file it; it only knows what’s on screen.