Bug reports are fastest to resolve when they describe what happened, where it happened, and how to reproduce it. Even a simple issue becomes easier to diagnose when those details are present.
BEFORE YOU START
- The page URL where the problem appears.
- A screenshot or recording if the issue is visual or intermittent.
- The device, browser, and steps used before the problem happened.
1
Describe the expected behavior
Explain what should have happened before you describe what failed. That gives the issue a clear target state for testing.
2
List the exact steps that produced the issue
Keep the steps short and ordered. If the issue appears only after login, form submission, or mobile interaction, say so explicitly.
3
Share supporting evidence
Include screenshots, recordings, timestamps, or any error message text. That is often the difference between a quick fix and a slow investigation.
If the issue affects checkout, payment, or security, mention that immediately. Those reports should be prioritized differently from routine cosmetic fixes.
Issue report ready
Once the URL, steps, browser details, and evidence are included, the report is ready for diagnosis and triage.