Bug report template for games
A bug report format that gets bugs fixed: what to write, what to attach and how to rate how bad it is.
Bug report template for games
A good bug report lets someone who has never seen the problem make it happen and know when it’s fixed. Most reports that go nowhere are missing one thing: the steps to reproduce it.
Put the symptom and the place in the title: “Game freezes when opening the inventory in the cave level” will be understood in a list; “Bug in inventory” won’t. Anyone should be able to tell two reports apart from their titles alone.
If you collect reports from players, ask for only what they can easily give: what happened, what they were doing and the platform. You can find the rest yourself.
Bug report template for games: part 1
- # [Short summary: what is wrong, and where]
- ## Severity
- [Critical / High / Medium / Low]
- ## Build
- - Game version / build number:
- - Platform and device:
- - Date and time:
- ## Steps to reproduce
- 1.
- 2.
- 3.
- ## Expected result
- [What should have happened]
- ## Actual result
- [What happened instead]
- ## How often
- [Always / Often / Sometimes / Once]
- ## Attachments
- - Screenshot or clip:
- - Log file:
- - Save file:
- ## Notes
- [Anything you tried, or anything that changes the result]
Bug report template for games: part 2
- Critical: crashes, corrupts or loses progress, or stops the player from finishing the game. Fix before anything else.
- High: a main feature doesn’t work, with no way around it.
- Medium: something is wrong, but the player can carry on or work around it.
- Low: cosmetic, or a rare edge case. A typo, a texture seam, a misaligned icon.