Bug report template
Give the next person enough detail to reproduce the problem. Start with a filled example, describe what should happen and what actually happened, then copy or download a Markdown report.
Free in your browser. No signup or upload.
Write a report someone can reproduce
Start with the demonstration below or a blank report. Your draft stays in this tab; copy or download it before closing.
The core fields are filled. Check the steps and evidence before sharing.
No account required. This template does not upload or save your draft, attach evidence, or create a Jira ticket.
Make the starting point clear
Include the account state, page and data needed before step one. Write one action per step, with the name of the button or field. State how often it happens, including when you have only seen it once.
Expected and actual results belong in separate fields. Someone reading the report should be able to tell where the behaviour diverged without guessing your intention.
Read Mozilla’s bug-writing guidelinesShow what the words cannot
A screenshot can show a wrong value or layout. A short recording can show a sequence, timing or an intermittent state. Review the visible details and choose evidence the recipient has permission to open.
Read the complete exampleThe example uses demonstration data. Replace it with your own observations; leave unknown details labelled as unknown.
Keep the evidence with the report
tautau’s reporting helper captures reviewed screenshots, recorded steps and bounded diagnostics in a private workspace. Use it when your report needs more than a text description.