When to Use This Message
Send a Bug Report when:
- You've encountered unexpected behavior, an error, or a crash in software.
- You want to give the development team enough detail to reproduce the issue.
- The bug is affecting your ability to use the product as expected.
- You want a documented report in case the issue needs to be tracked over time.
Message Writing Tips
- Describe the Exact Steps to Reproduce: List what you did right before the bug occurred — this is the single most useful thing for a development team.
- State What You Expected vs. What Happened: Clearly separate the expected behavior from the actual, incorrect behavior.
- Mention Your Environment: Note your device, browser, app version, or operating system, since bugs are often environment-specific.
- Include Error Messages If Any: Copy the exact text of any error message — exact wording can help developers pinpoint the cause faster.
Frequently Asked Questions
What makes a bug report most useful for developers?
Clear reproduction steps, the expected vs. actual behavior, and environment details (device, browser, version) — these let developers reproduce and fix the issue faster.
Should I include screenshots or screen recordings?
Yes, if possible — visual evidence often clarifies issues that are hard to describe in text alone.
What if I can't consistently reproduce the bug?
Mention this explicitly, along with how often it seems to happen and any pattern you've noticed — intermittent bugs are still valuable to report.