Skip to content
WorkspaceTemplates
The first pages of the Game Bug Report template

Game Bug Report

Document template for Google Docs and Word

Make a copy in Google Docs
Type
Document
Price
Free
Pages
8 · US Letter
Style
Corporate
Difficulty
Beginner
Updated
November 6, 2026

Every page (8)

Overview

A bug report that says it does not work sends the developer on a search, and a report with no build number can send them to the wrong code. This template gives one defect its own report, with the build, platform, steps to reproduce, reproduction rate, video evidence and a severity rating with a fix target. Each page answers one question a developer or triage lead would otherwise ask, so the defect can be fixed or closed cleanly.

The sample is for Rookwood Cloud, a fictional cloud gaming service, and a save bug on build 8.4.2 that appears in three of five runs on iOS and Android. Replace the summary, build, environment and steps with your own, attach the log excerpt and video with personal data removed, and set severity against your triage definitions. Keep one defect per report, so each one can be closed on its own.

Useful for

  • A tester filing a defect on a new build before the weekly triage meeting
  • A triage lead reviewing open defects by severity before a release decision
  • A QA team training new testers to write reproducible bug reports

What's included

  • Build page with the architecture diagram and the save request flow
  • Platform page with the environment table and what is recorded each time
  • Steps page with a five-step reproduction flow and an escalation path
  • Repro rate page with platform cards and the meaning of each rate
  • Video page with the clip notes and the logs to attach
  • Severity page with a timeline, the severity scale and a release decision

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the summary with one sentence of observable behavior, then fill in the build and environment.

  3. 3

    Rewrite the steps so someone else reproduces the defect on the first try, and attach a log or video.

  4. 4

    Remove personal data from every attachment, then set severity against your own triage definitions.

  5. 5

    Delete the guide page, then share the report with the team or present it from Google Docs.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Are Rookwood Cloud, the game and the build real?

No. Rookwood Cloud, the test accounts, the build numbers, the defect and every log line are fictional sample data. Replace them with your own before you file a real defect.

How many defects belong in one report?

One. A report with two defects cannot be closed cleanly, because one fix may resolve only half of it. Split the report, link the two, and give each its own severity and steps.

Should testers rate severity?

Testers suggest a severity using the written definitions, and the triage lead confirms it. Rating by complaint volume is not allowed, because impact on players, not the number of reports, sets the fix target.

  • #bug-report-template
  • #game-testing
  • #defect-report
  • #qa-triage
  • #severity-rating

Related templates

More Google Docs templatesMore developer workflows templates

More bug report templates

See all 5

Also in Developer workflows

All developer workflows templates
Get this template

    What you get

      Use this templateSee full details

      Preparing your template…