Founding price: the first 100 buyers get Pro for life at $24 once (then $39).Founding: Pro for life $24 Get notified →
Free templates

Bug triage meeting agenda (defect triage)

A triage meeting has one job: every new bug leaves with a severity, a priority and an owner, or gets closed with a reason. This 30-minute agenda from our Bug Report & QA Kit keeps it to decisions, not debugging.

Quick answer

Run it for 30 minutes, once or twice a week: 5 minutes on open S1/S2 bugs, 15 on new issues (severity, priority, owner), 5 on stale issues, 5 on patterns. Rule one: decide, don't debug.

Who attends

Facilitator (rotates), product owner, one engineer per team, QA, support representative.

The agenda

TimeBlockWhat happens
0–5 minOpen S1/S2 checkEvery open S1 and S2: owner, status, next update. No discussion longer than 1 minute each.
5–20 minNew issuesFor each "needs-triage" issue: reproduce or ask for info, set severity (guide), set priority (matrix), assign owner or close with a reason.
20–25 minStale issuesAnything "needs info" for 14+ days: close with a note. Anything P3 untouched for 90 days: close or re-justify.
25–30 minPatternsWhich area produced the most bugs? Any process change (test, checklist item, monitor) to propose?

Rules

  1. Decide, do not debug. If it needs more than 2 minutes, assign someone and move on.
  2. Severity comes from the guide, not from who is loudest.
  3. Every closed issue gets a one-line reason.
  4. Support leaves with an answer for every customer-reported issue.

Copy the agenda

Triage agenda (calendar invite / doc)Paste into the invite
Bug triage meeting (30 minutes, weekly or twice a week)
Who: Facilitator (rotates), product owner, one engineer per team, QA, support representative.

0–5 min  Open S1/S2 check
    Every open S1 and S2: owner, status, next update. No discussion longer than 1 minute each.
5–20 min  New issues
    For each "needs-triage" issue: reproduce or ask for info, set severity (guide), set priority (matrix), assign owner or close with a reason.
20–25 min  Stale issues
    Anything "needs info" for 14+ days: close with a note. Anything P3 untouched for 90 days: close or re-justify.
25–30 min  Patterns
    Which area produced the most bugs? Any process change (test, checklist item, monitor) to propose?

Rules
1. Decide, do not debug. If it needs more than 2 minutes, assign someone and move on.
2. Severity comes from the guide, not from who is loudest.
3. Every closed issue gets a one-line reason.
4. Support leaves with an answer for every customer-reported issue.

Set severity with the severity guide and priority matrix; it is what makes the 15-minute block fit.

Record the video part

Ask reporters to attach a short recording: most "can't reproduce" debates in triage end when everyone can watch the bug. Bobbin is a free Chrome extension that records your screen, a window or a tab with your microphone and an optional webcam bubble. No account, no watermark, no time limit, and nothing is uploaded: the file stays on your computer.

  1. Click the Bobbin icon in Chrome's toolbar and choose Record screen, window or tab.
  2. Pick your microphone and turn on the camera if you want the webcam bubble.
  3. Press Start recording, choose what to share in Chrome's picker, and wait for the 3-second countdown.
  4. Pause with Alt+Shift+P, stop with Alt+Shift+S, then press Download to save the file.

To keep other tabs and notifications out of it, share just the Chrome tab (the webcam bubble appears only in screen and window recordings). Bobbin saves MP4 where your browser supports it (Chrome 126 or newer), WebM otherwise, and tells you which it used.

File size: our 60-minute 1080p test came to about 246 MB (roughly 4 MB a minute) on a simple synthetic screen; busy real screens can be larger, so a 1–2 minute clip is usually small enough to attach.

From The Bug Report & QA Kit

The kit also has a bug bash runbook and Sheets / Notion trackers. The full kit: 10 bug templates for GitHub, Jira, Linear and Markdown, 9 release checklists (126 checks), the severity guide, 8 bug-video scripts and trackers.

See the QA kit ($15, one-time) PDF + ZIP · 7-day refund · more free samples on the page

Frequently asked questions

What is a bug triage meeting?

A short, regular meeting where new bugs get a severity, a priority and an owner, or are closed with a reason.

Who should attend defect triage?

Facilitator (rotates), product owner, one engineer per team, QA, support representative.

How often should you hold bug triage?

Weekly or twice a week for most teams; daily during a launch or bug bash.

Record your screen and camera. Keep the file.

Free, no account, no watermark, no time limit. Saves an MP4 on your computer.

Launching on the Chrome Web Store soon. The Install page has the link as soon as it is live.