Free tool
Bug Triage Template: Editable Worksheet
Use a bug triage template to record impact, evidence, ownership and your team’s decision. Edit a local worksheet, then copy or download Markdown and CSV.
Turn one bug report into a next action
A bug triage template records the affected task, evidence, reproducibility, owner and a team decision with a reason. Use this worksheet to review one report, explain what is still unknown, and assign a concrete next action. Edit the fields, then copy or download Markdown or CSV without signup.
Your team chooses the decision. The worksheet does not calculate severity, assign priority, promise a response time or diagnose an incident.
Name the observed failure, without guessing its cause.
Who is affected, what cannot be done, and is there a workaround?
Describe the timing constraint and why it matters. No priority is assigned automatically.
List reviewed filenames or references; this tool does not capture, open or attach evidence.
Choose what was actually tested; record attempts and environment in your evidence notes.
Name the person or team responsible for the next action.
Choose your team's decision. These are worksheet labels, not a universal triage policy.
Explain the decision using observations, constraints and remaining unknowns.
Write a concrete follow-up the owner can carry out.
Completeness and review gaps
- Missing or unknown: Report title
- Missing or unknown: Impact on people or task
- Missing or unknown: Urgency and reason
- Missing or unknown: Evidence references
- Missing or unknown: Reproducibility
- Missing or unknown: Owner
- Missing or unknown: Review decision
- Missing or unknown: Decision reason
- Missing or unknown: Next action
Limits: title and owner 200 characters each; evidence 4,000; other text fields 2,000. Preview text updates from the fields. Review private details before sharing; no privacy review is performed automatically.
CSV export quotes every cell and adds a visible Text: prefix to formula-like values. The original text follows that prefix. Spreadsheet import and re-save behavior varies; review the import settings and resulting cells before sharing.
Read-only output. Edit the worksheet fields above to change it; select this text to copy manually.
Read-only output. Edit the worksheet fields above to change it; select this text to copy manually.
Two fictional triage decisions, with reasoning
These teaching examples are invented, not captured customer reports. Load either into the worksheet to inspect or change the reasoning. Exports keep the fictional label; reset to blank for your own report.
Checkout failure: investigate the missing reproduction
A test buyer sees an error after Place order. The purchase task appears blocked, but one screenshot cannot establish how many buyers are affected or what caused the failure.
The fictional checkout team chooses Investigate. Reproducibility stays Unknown, so the worksheet remains an incomplete draft. The next action is to repeat the purchase on staging and record the starting state, steps, browser, release and outcome.
A serious possible impact is a reason to investigate; it is not evidence of a confirmed widespread incident. The owner can revisit the decision when observations improve.
Mobile overlap: schedule a fix with a tested workaround
A Help label overlaps an icon at a 390px viewport. In three fictional staging attempts, opening Help from the menu still completes the task.
The fictional interface team chooses Schedule because this observed cosmetic issue has a usable workaround. The owner will check spacing at narrow widths, then retest the menu after the change.
This decision belongs to the example team. If users cannot read the label or the workaround fails in another environment, record that evidence and review the decision again.
Revisit a decision when the evidence changes
A workaround is a claim to verify
In the fictional mobile overlap example, Schedule depends on the Help menu still completing the task. If a later test finds keyboard users cannot reach that menu, record the new environment, steps and actual result. Reassess impact and urgency with the owner; do not preserve Schedule just because the original screenshot looks cosmetic. Conversely, a single checkout error with unknown reproducibility calls for a concrete investigation step, not an invented incident scope.
Microsoft’s Azure Boards bug guidance separates severity from priority. This worksheet leaves both the next action and the reason with your team.
How to use and review the worksheet
- Record impact before choosing an order. Describe the affected person or task, the observed consequence and any tested workaround. Separate that from the timing constraint in Urgency and reason.
- Keep unknowns visible. Blank text exports as Not provided; unselected reproducibility and decision export as Unknown. Missing fields mark the output Incomplete draft. A filled field means an answer was entered, not that it was verified.
- Make a human decision. Choose Investigate, Schedule, Defer or Close only after your team reviews the evidence. Explain why, assign an owner and write the next action. These labels do not replace your team's policy.
- Review the export. Markdown escapes pasted formatting and raw HTML. CSV quotes every cell and visibly prefixes formula-like text with Text: instead of relying only on an apostrophe. Importers and re-saving can behave differently; review the imported cells. Neither format redacts private information or verifies attachments.
Microsoft’s Azure Boards bug guidance distinguishes impact severity from resolution priority and describes process-specific fields. This worksheet uses that distinction without copying numeric labels as universal rules. The export precaution follows OWASP’s CSV injection guidance; it is not a guarantee for every spreadsheet application.
Need better input first? Use the reproduction steps guide, bug report generator, screenshot annotator and HTTP status evidence guide. Compare the sample bug reports before handing off your worksheet.
Published October 9, 2026. Updated October 10, 2026. Method: an original one-report workflow with bounded fields, manual decisions, completeness checks and local text exports. Worksheet contents stay in the current tab until you copy or download them; this tool does not store or upload the fields. Existing site analytics may record a completion event, without worksheet text.
Examples for your team
Builder example
Fictional builder example: a checkout failure blocks a test purchase; the team asks for reproduction evidence before choosing a resolution order.
Start your 14-day free trialAgency / QA example
Fictional agency / QA example: a mobile label overlaps an icon; a workaround keeps the task usable while the team schedules a layout fix.
Start your 14-day free trial