Task boards
Bug triage board template
New to Closed with a Confirmed gate: no fix work starts on an unreproduced report.
Last reviewed July 17, 2026
A Linear-format CSV for a bug triage board: intake, confirmation, fixing, and verification columns with severity-labeled seeded rows.
Columns
NewConfirmedIn ProgressVerifyingClosed
Board CSV (Linear format)
Title,Description,Status,Priority,Labels Export hangs on files over 50MB,Two reports this week; needs repro on staging,New,High,bug Wrong currency symbol for CAD accounts,Repro confirmed; formatting layer suspected,Confirmed,Medium,bug Login loop after password reset,Repro steps in the report; affects all browsers,Confirmed,Urgent,bug Dashboard chart off by one day,Timezone handling; fix in review branch,In Progress,High,bug Notification emails duplicated,Fix deployed to staging; verify with test account,Verifying,Medium,bug Search ignores archived items toggle,Cannot reproduce; waiting on reporter details,New,Low,needs-info Crash on paste of large table,Fixed in 2.4.1; confirmed by reporter,Closed,High,bug Settings page slow on large teams,Profiling scheduled; suspect member list query,Confirmed,Medium,performance
Set it up
- 1
Copy the CSV
Save as bug-triage.csv; the needs-info label marks reports waiting on the reporter, not on you.
- 2
Import it
Linear-format import at /help/import-linear; keep severity in Priority and type in Labels.
- 3
Enforce the Confirmed gate
Nothing moves to In Progress without reproduction steps; the QA test runner agent can do the confirming.