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

Bug Report

Document template for Google Docs and Word

Make a copy in Google Docs
Type
Document
Price
Free
Pages
8 · US Letter
Style
Minimal
Difficulty
Beginner
Updated
October 30, 2026

Every page (8)

Overview

Bug reports fail when they say it doesn't work and leave out the steps, build and expected result. This template keeps one defect per report: an answer-first summary with severity, reproduction steps, expected and actual behaviour, the environment and the evidence to attach.

The sample reports defect DW-2417 at Driftwood Software, where a percentage voucher sets the iOS checkout total to £0.00 in 5 of 5 runs on build 8.4.2 (1,284). Replace the summary with one sentence of observable behaviour, then fill in your build, steps, severity and attachments.

Useful for

  • A tester filing a reproducible defect with the build, device and evidence a developer needs
  • A triage lead checking severity, impact and fix target before a release meeting
  • A support agent passing a customer's problem to engineering with the steps already confirmed

What's included

  • Summary page with headline figures, key facts and a recommendation
  • Steps to reproduce as a four-step flow, plus what to do if it does not repeat
  • Expected-result page with a title block, key figures and three checks
  • Actual-result article with log evidence, who is affected and a workaround
  • Environment page with the diagnostics command, fields and an example output
  • Attachments diagram, log-export reference and a make-it-yours guide

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 behaviour, not a theory of the cause, and rewrite the steps so someone else reproduces it on the first try.

  3. 3

    Fill in the environment with the build, device, OS and account type where it happens, and set severity and priority from your triage definitions.

  4. 4

    Attach the log excerpt, recording or network trace, and remove personal data and secrets from every file.

  5. 5

    Delete the guide page, then share the report with the triage lead and the developer.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

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

Questions

Should one report cover several bugs?

No. Keep one defect per report so each can be assigned, fixed and closed cleanly. If two faults share a cause, link the reports rather than merging them.

How do I set severity?

Use impact, not the volume of complaints. The sample uses S1 to S4 with fix targets of 24 hours, 3 days, next release and backlog; adjust them to your triage rules.

Are the company, people and figures real?

No. Driftwood Software, the people, the build numbers and every figure are fictional sample data. Replace all of them with details from your own defect.

  • #bug-report
  • #defect-report
  • #bug-tracking
  • #steps-to-reproduce
  • #qa-template
  • #developer-workflows
  • #google-docs

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…