Browse the docs
Worked example
File a bug report developers can reproduce
Record the exact steps once, mark what went wrong, and paste Markdown into your issue tracker.
- Plan
- Free
- Reading time
- 1 min read
- Checked against Thoth for Windows on
- October 23, 2026
The situation
A customer says “Save does nothing” in the billing screen. Engineering needs the exact clicks, the data, the screen after each one and what was expected.
What you end up with: A Markdown issue with numbered steps, an image for each, the expected and actual result in a callout, and the page address of each step.
- For
- QA, support and product
- Takes about
- 10 minutes
- 1
Reproduce it while recording
Start Capture steps on Clicked window or the browser window, and trigger the bug. Thoth records the clicks, the values you typed (never in password fields) and, in a browser, the page each step happened on. Make sure Remember app and page address is on (Settings → Privacy).
- 2
Stop at the failure
Press Ctrl+Alt+C to capture the moment it fails, with the error message on screen. Then finish.
- 3
Say what you expected
On the last step, add a Warning note titled
Expectedand one titledActual. Give the data you used in the description:Invoice total 120.00, VAT 20%. - 4
Remove what isn’t needed
Delete detours and blur anything private. Run Check this guide for leftovers.
- 5
Paste into the issue
Choose Copy → Copy as Markdown and paste into the issue. For images, Export → Markdown writes the
.mdfile with an images folder to drag in; notes become GitHub alerts.