CBSE.CLUB

Kanban template · Software and product

Bug tracking kanban board template

A bug tracker does not need forty fields. It needs a place for new reports, a clear owner, and a way to make sure the fix really works.

Use this template, freeSee all templates

Who this board is for

Small software teams, indie developers, QA testers and support people who report bugs. It suits teams who find Jira too heavy and a spreadsheet too loose. Support staff can file into Maybe? without needing to know how engineering works.

The columns, and what each one means

Maybe?
Every new card lands here first. Decide whether it is real work before it takes a slot on the board.
Confirmed
Reproduced and understood. Has steps to reproduce and an idea of how bad it is.
Fixing
Someone is working on a fix. Link the branch or pull request in a comment.
Verify
Fix is merged or deployed. Someone other than the fixer checks it before it is closed.
Done
Close a card when it is finished. Closed cards keep their history and can be reopened.
Not Now
Cards nobody touches for 30 days (or the period you choose) move here on their own, so the board only shows live work.

How to run it

  1. Anyone can file a bug into Maybe?. Ask for: what happened, what you expected, and steps to reproduce.
  2. Triage Maybe? daily: reproduce it, tag severity and area, then move it to Confirmed, close it as “can’t reproduce”, or send it to Not Now.
  3. Gild anything that is hurting customers right now; gold sits at the top of Confirmed.
  4. When you pick up a bug, assign yourself and move it to Fixing. Keep it to one or two per person.
  5. After the fix ships, move to Verify. Whoever reported or tested it confirms and closes it.

Suggested tags

#bug a defect, not a feature request#p1 customers are blocked#web, ios, api which part of the product#regression it used to work

Tips from teams who use this board

  • Set the board’s auto-postpone to 30 days: a report nobody has touched in a month is rarely real.
  • Add a webhook to your team’s Slack channel for “card published” so new reports are seen quickly.
  • Use a CSV import to bring over an existing bug list from a spreadsheet.
  • Put the card number (#123) in your commit messages so people can find the discussion.

Frequently asked questions

Can I use kanban for bug tracking?

Yes. Kanban suits bug work well because bugs arrive unpredictably. A triage column, a WIP-limited fixing column and a verify step cover most teams.

How do I record severity?

Use tags such as #p1 and #p2, and gild the few bugs that must be fixed first. Filters can then list every #p1 across all boards.

Can customers report bugs directly?

Customers do not need accounts to view a public board, but filing cards requires an account. Many teams paste customer reports into Maybe? from their support inbox.

Start your bug tracking board in a minute.

Free for everyone. Unlimited boards, cards and people. No credit card, no AI.

Use this template