Free tool
Bug-report generator
Turn reproduction notes into a structured Markdown bug report that you can review, copy, and share with your team.
Build a report developers can reproduce
Write what happened, keep unknown details explicit, then copy or download the Markdown for your issue tracker. No signup is needed to use the generator.
Start blank, or load a labelled example. Reports stay in this browser tab. Fields are capped at 200 characters for the title, 4,000 for steps and evidence, and 2,000 for each other answer.
Name the observed failure, not a guessed cause.
Write one action per line; the report will number them.
Include browser, device, operating system, page, and viewport when known.
List filenames or links you have reviewed; the tool does not capture or upload evidence.
Completeness checklist
Missing details stay marked in the export. Check each item before sharing.
- ○ Missing: Title
- ○ Missing: Reproduction steps
- ○ Missing: Expected result
- ○ Missing: Actual result
- ○ Missing: Environment
- ○ Not provided: Evidence references (optional)
Markdown preview
# Not provided
## Reproduction steps
Not provided
## Expected result
Not provided
## Actual result
Not provided
## Environment
Not provided
## Evidence references
Not provided
## Completeness checklist
- [ ] Title — not provided
- [ ] Reproduction steps — not provided
- [ ] Expected result — not provided
- [ ] Actual result — not provided
- [ ] Environment — not provided
- [ ] Evidence references (optional) — not provided
Examples for your team
Builder example
A builder records a save failure: open a draft, change its title, save, and compare the expected title with the unchanged result.
Start your 14-day free trialAgency / QA example
An agency tester records the client staging URL, the tested browser, the affected form, and the expected confirmation message.
Start your 14-day free trial