Projects

Bug tracker template

Bugs with severity, status, area and steps to reproduce, sorted so the worst ones are on top.

6 database rows

Use this template Draft a variant with AI

🐞

Bugs

Bug	Severity	Status	Area	Reported	Assignee
Payment page blank in Safari 17	Critical	Fixing	Billing	17 Oct 2026	Leo
Search misses pages with umlauts in the title	High	Confirmed	Search	14 Oct 2026	Malik
Undo removes two blocks instead of one	Medium	New	Editor	16 Oct 2026
Login link expires after 5 minutes instead of 15	Medium	Fixed	Login	9 Oct 2026	Ana
Keyboard covers the save button on small Android phones	Low	New	Mobile	12 Oct 2026
Invoice number font differs in the PDF	Low	Won't fix	Billing	28 Sept 2026	Ben

This is the page you get. Every block and row is editable.

What it is

A bug tracker lists every reported bug with its severity, status, product area, reporter and assignee. Severity says how bad it is for users. Critical means people can't use a core feature. Each bug page holds steps to reproduce, the expected result and the actual result, which is what a developer needs to fix it.

When to use it

Products with users reporting problems
QA before a release
Teams that track bugs in chat and lose them

How to use it

01
Report with steps
Open a bug and write numbered steps to reproduce, then expected and actual. A bug nobody can reproduce rarely gets fixed.
02
Triage by severity
The Worst first view sorts by severity. Review new bugs daily and set status to Confirmed or Won't fix.
03
Group by area
The board by area shows which part of the product breaks most.
04
Share with QA
Share the tracker with your testers with edit access, so they log bugs here instead of in chat.

Or have the AI draft your version

"Create a bug tracker for an online booking system with severities, statuses, areas for payments, calendar, email and admin, browser and device properties, and five sample bugs."

Draft a variant with AI

All templates

Projects
Sprint board
Tickets for the current sprint on a board from backlog to done, with points, type and assignee.
🧯
Post-mortem: invoice emails delayed
Blameless. We look at how the system let this happen, not at who pressed the button.
Summary
For 3 hours and 20 minutes, invoice emails queued but did not send. 1,840 invoices went out late. No data was lost.
Impact
1,840 invoice emails delayed by up to 3 hours 20 minutes
37 support tickets
No duplicate or lost invoices
Timeline
08:12 Deploy 4.1.3 goes out with a new email provider setting
08:15 Email queue starts growing
10:40 Support notices tickets about missing invoices, pages on-call
11:05 On-call finds the setting points to the sandbox account
11:20 Rollback to 4.1.2
11:32 Queue drained, all emails sent
Root cause
The production and sandbox email keys share one variable name in two config files. The deploy read the wrong file. Nothing alerted on a growing queue, so we found out from customers.
What went well
Rollback took 15 minutes
Queued emails were kept and sent, nothing had to be re-created
What didn't
2 hours 25 minutes between the problem starting and anyone knowing
Actions
Ana: alert when the email queue is over 200 for 10 minutes, by Friday 23 October
Malik: one config file per environment, rename the sandbox variable
Rosa: template reply for support when emails are delayed
Tobias: email affected customers with an apology
Docs
Incident post-mortem
A blameless write-up of an incident: timeline, impact, root cause and actions that stop a repeat.
Draft your own with AI
Describe the page you need in one sentence. The AI writes it, and you edit it like any other page.
How the AI works

🐞Bug tracker template

What it is

When to use it

How to use it

Report with steps

Triage by severity

Group by area

Share with QA

Or have the AI draft your version

Related templates

🏃Sprint board

🧯Incident post-mortem

Draft your own with AI

Cookies and storage

Bug tracker template

Sprint board

Incident post-mortem