QA Bug Reports: Stage Repro Steps, Logs, and Screenshots

Stage a bug report as a small packet before you open the tracker: one text block with the title, build and numbered steps; the exact command or trimmed log line that shows the failure; and the screenshot saved as a file with a matching name. Then paste the text into the issue, attach or drag in the image, and delete any clipboard items that held account IDs or tokens. The clipboard is a staging table for the few minutes between reproducing a bug and filing it, not the place the evidence lives.

The five-part repro packet

Writing the title, environment and steps as one block means one copy and one paste, instead of five separate clipboard items to keep in order. Use a redacted or test account ID, never a real password.

If you need more than these five parts, the extra evidence belongs in attachments, not in a longer clipboard stack.

Keep the command next to its screenshot

A command without its output is half a report: the developer runs it and can't tell whether what they see is the bug. A screenshot without the command is the other half. Keep them together:

1. Reproduce the bug.
2. Copy the exact command or the steps you ran, and paste them into a text file.
3. Capture the failure as a screenshot and save it.
4. Give the files the same base name, such as repro-header-overflow.txt, repro-header-overflow.png and, if there's terminal output, repro-header-overflow.log.
5. When you file the issue, paste the command into a fenced code block, attach the screenshot, and attach or paste the log.

Matching names make the set easy to find later and easy to delete together once the bug is fixed.

Capture screenshots that survive

• Windows logo key + Shift + S lets you select a region and copies it to the clipboard. On Windows 11, Snipping Tool also saves snips to your Screenshots folder by default.
• Print Screen opens the same selection tool on Windows 11 by default. If you've turned that off in Settings > Accessibility > Keyboard, it copies the whole screen to the clipboard instead.
• In Snipping Tool, Ctrl+S or Save as saves the snip where you choose.

Crop to the failing control. A full multi-monitor capture is hard to read and can exceed the 4 MB per-item limit of Windows clipboard history, so it won't appear in Win+V even though Ctrl+V still pastes it until your next copy. Save the file and attach that. Print Screen vs Win+Shift+S vs Snipping Tool compares the capture options, and why your huge screenshot never appears in Win+V explains the size limit.

Attach evidence in Jira and GitHub

Jira Cloud

• Drop a file onto the open work item to attach it, or use the Add button under the summary and choose Attachment.
• You can also drop or attach files in comments and other long text fields, and paste content into the description editor.
• By default each file can be up to 10 MB, but your Jira admin can change that.

GitHub issues

• Drag and drop a file into the comment box, or select the Attach files paperclip and choose it.
• In many browsers you can paste an image directly into the comment box.
• Images and GIFs can be up to 10 MB and most other files up to 25 MB. Text formats including .txt, .log and .json are supported.

For chat triage before filing, pasting a snip into Discord, Slack and Teams covers each app. Chat is for discussion; the tracker is the record.

Logs, payloads and commands

• Copy the smallest piece of log that shows the failure: the exception line, the request ID, or a few lines around it. Copying error logs without grabbing half the console shows how to select cleanly.
• Attach the full log as a file if the developer will need it, rather than pasting thousands of lines into the description.
• Keep request bodies as files too; JSON payloads belong in files, not clips explains why.
• Redact tokens, cookies and customer data before you copy, not after.

Keep secrets out of the packet

Testers copy secrets because the form is right there: staging passwords, bearer tokens from DevTools, .env lines, connection strings. Don't put any of them in the packet, and never pin them in Win+V.

Some password managers mark their copies so Windows clipboard history skips them, but text you copy from a log, a config file or DevTools carries no such mark. If a token does land in history, press Win+V, select See more (...) next to it and choose Delete, then treat the token as exposed. Is an API key on the clipboard a security incident? covers what to do next.

A bug-bash loop

1. Turn on clipboard history if you want it (Win+V, then Turn on). Leave Clipboard history across your devices off on shared test machines.
2. Reproduce the bug once, cleanly, so history isn't full of failed attempts.
3. Write the title, environment and steps in your editor and copy them as one block.
4. Capture and save the screenshot. Copy the command or log line.
5. Open the tracker, paste the text block, attach the screenshot and log.
6. Press Win+V and delete the items that held IDs or payloads, or select Clear all.
7. Repeat for the next bug.

Unpinned history is cleared when the PC restarts, so file before you shut down. Anything you haven't filed by then survives only as saved files.

Using a clipboard shelf for the packet

Win+V is enough when you file each bug within a few minutes. If you collect evidence for several bugs before writing them up, a clipboard manager that keeps images and files can help. In Edge Drop, screenshots and files copied in Explorer appear as cards on a shelf at the screen edge, and you can drag an image or file card straight into the tracker's upload area. Text cards, such as your steps block, can't be dragged; click them to paste into the app you were using. To keep one bug's screenshots together, drag one image card onto another; a stack holds up to 10 items.

Before copying credentials or customer data, turn on Incognito mode so Edge Drop doesn't record them; how to use Incognito mode in Edge Drop has the steps. Like Win+V, a shelf is a staging area for one tester on one PC, not test management or a shared evidence store. Once the ticket is filed, delete the packet.

FAQ

Why doesn't my screenshot appear in Win+V?

It's probably over 4 MB, the per-item limit for clipboard history. Ctrl+V still pastes it until your next copy, but saving the file is safer.

Can I paste a screenshot straight into a GitHub issue?

In many browsers, yes: click the comment box and press Ctrl+V. If nothing happens, save the image and drag it in.

Should I pin my test account or build number?

Pin only non-secret text you reuse all day, such as an environment URL, and update or delete it when the build changes. Never pin passwords or tokens.

Related reading

• How to Copy an Error Log Without the Noise
• Print Screen vs Win+Shift+S vs Snipping Tool (Windows 11)
• Copied an API Key or .env File? What to Do Next
• How to Keep Your Last Ten Screenshots Handy on Windows

Sources

• Add files, images, and other content to describe an issue (Atlassian Support) — attaching and dropping files in Jira Cloud, default 10 MB file limit.
• Attaching files (GitHub Docs) — drag, paste and attach in issues; supported file types and size limits.
• Use Snipping Tool to capture screenshots (Microsoft Support) — Print Screen, saving snips, Screenshots folder.
• Keyboard shortcuts in Windows (Microsoft Support) — Win+Shift+S copies a screen region to the clipboard.
• Using the clipboard (Microsoft Support) — 4 MB limit, deleting items, restart clearing, sync setting.
• Clipboard Formats (Microsoft Learn) — formats apps use to keep copies out of clipboard history.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge Drop vs Win+V · Support