Bug Tracking Board: From Intake and Repro Check to Released Fix

プロジェクト管理・開発

Bug Tracking Board: From Intake and Repro Check to Released Fix

Opened by the development team the day a bug report lands, and kept in use until the fix ships. The whiteboard leads with an impact-by-frequency matrix that sets the order of work, plus triage ground rules, a repro-steps template with worked examples, the six stages from intake to release, and how to call it when a bug won't reproduce. The task board runs from Reported through Reproducing, Fixing and Verifying to Released, and starts with five parent tasks - intake, repro, fix, release and follow-up - each with its own subtasks.

0 いいね 0 コピー 作者: WeProcess
bug tracking QA defect triage repro steps release verification
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 Bug Tracking Board: From Intake and Repro Check to Released Fix
無料登録してこのテンプレートを使う

ホワイトボード プレビュー

1. Ground Rules for Bug Work (agree t... 2. Impact x Frequency (what to pick u... Severe / happens sometimes Severe / happens always Minor / happens sometimes Minor / happens always 3. Repro Steps Template (paste it int... 4. From Intake to Released Fix 5. When It Won't Reproduce 6. Check Before You Fix 7. Before You Close It Bug Tracking Board How to use: 1. Tu... Priorities & ... Working rules Stop-the-line &am... Examples & fi... One way inEvery report becomes a card here. If it arrives over chat, whoever sees it makes the card first, then replies. Impact sets the orderNot first come, first served. Place the bug on the matrix below, then assign an owner. When to stop the lineData loss in production, or double charging. Either one outranks whatever is in progress. Severity examplesSev1: checkout fails for everyoneSev2: saving breaks on one browserSev3: layout glitch 縦軸: Impact (minor... Fix it this sprint. The trigger is usually unclear, so spend the first pass narrowing the conditions. Top priority. Drop other work, and ship a workaround to stop the bleeding before the cause is known. Let these collect and fix them next time you're in that code. Close anything untouched for three months. Everyone hits these daily, so they wear people down. Clear the cheap ones on a regular cadence. 1. EnvironmentOS / browser / app version / plan.e.g. macOS 15, Chrome 130, paid plan 2. StepsNumbered, fine-grained enough for a stranger to follow.e.g. 1. Open a project 2. Clear the due date 3. Hit Save 3. Expected vs actuale.g. Expected: it saves and returns to the list. Actual: Save stays grey and nothing happens. 4. Frequency & evidencee.g. 5 out of 5 attempts. Attach a screenshot and the console error, and note the time it happened. 1. IntakeTurn the report into a cardCheck all four template fields are filled in, and go back to the reporter if not. 2. TriagePlace it on the matrixImpact and frequency pick the quadrant, which picks the order and the owner. 3. ReproFollow the steps yourselfRun the same steps and see if it happens. If not, vary the conditions and try three times. 4. DiagnoseNarrow the causeWork out when it started and compare with recent changes to find the code involved. 5. Fix & verifyTest first, then fixAdd a test that catches this exact bug, fix it, and check the result in a production-like setup. 6. ReleaseClose the loopConfirm it's gone in production, then tell the reporter and lift the workaround you asked for. Suspect a missing step - ask for a screen recording Suspect the environment - version, network, extensions Three honest attempts, then hand it back Say what you already tried when you hand it back When did it start? Compare with recent changes Any other reports with the same cause? Can a workaround go out today? A test now covers this bug Verified fixed in production The reporter has been told Causes get reviewed monthly for patterns
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Reported 16件

Set up bug intake
Reproduce the bug
Fix the root cause
Verify and release
Share and close out
Share a report form
Set severity levels
Replay the steps
Check environments
Return no-repro bugs
Locate the cause
Add a guard test
Retest the fix
Check release steps
Tell the reporter
Review the patterns

Reproducing 0件

Fixing 0件

Verifying 0件

Released 0件