All templates

1 to 2 weeks · 4 milestones · 14 tasks

Bug Bash

Freeze features, hunt on every platform, fix by severity, verify, ship a patch.

Bug fixing without a structure means fixing whatever was reported last. This runs it as four phases with a hard rule: criticals before anything, lows go to the cut list.

Best when: Before a demo, a festival build, a release, or any time the bug board stops being trustworthy.

Use this template in Questlog

M1Prepare

Days 1 to 2 · 3 tasks
  1. Freeze features and create the bug-bash buildCodeurgent

    Tag the commit. Nothing new ships until this build is clean.

  2. Write the test matrix: platforms × core flowsDesignhigh

    Rows are platforms, columns are flows: new game, load, each level, settings, quit.

  3. Agree severity rulesOtherhigh

    Critical blocks progress or loses data. High breaks a feature. Medium is wrong but survivable. Low is cosmetic.

M2Hunt

Days 3 to 6 · 5 tasks
  1. Play start to finish on each platformOtherurgent

    One full run per row of the matrix. Log as you go.

  2. Visit every menu, every screen, every buttonOtherhigh

    Including the ones you think nobody clicks.

  3. Edge cases: alt-tab, resize, controller unplug, save during loadCodehigh

    The boring crashes that reviews mention.

  4. Fresh install on a clean machineCodehigh

    No dev tools, no leftover saves, no fonts you installed years ago.

  5. Log every find on the bug board with repro stepsOtherurgent

    Steps, expected, actual, severity, platform. One bug per card.

M3Fix

Days 7 to 10 · 4 tasks
  1. Triage: severity and owner on every bugOtherurgent

    Thirty minutes, whole team. Argue about severity, not about blame.

  2. Fix all critical bugsCodeurgent

    Nothing else starts until this column is empty.

  3. Fix the high bugs that fit the time boxCodehigh

    Time box is the deadline minus two days for verification.

  4. Move medium and low bugs to the cut list or next milestoneOtherlow

    Write the reason on each. Known issues beat forgotten ones.

M4Verify

Days 11 to 14 · 2 tasks
  1. Regression pass on every fixed bugOtherhigh

    Same repro steps, same platform, someone other than the fixer.

  2. Ship the patched build with a changelogOtherurgent

    List what was fixed and what is still known. Players respect the second list.

Start with this plan on your own board

Create a free project and the milestones and tasks are waiting for you.

Use this template