Writing about bugs
Practical notes on tracking bugs when your whole team fits round one table. No sprint ceremonies, no story points — just what works at small scale.
How to write a bug report that actually gets fixed
Most reports fail because the developer cannot reproduce the problem and has to come back and ask. What to include, what to leave out, why you should report observations rather than diagnoses — and a template you can paste straight in.
Bug tracking for a team of one to five
Most bug-tracking advice assumes a QA department and a release manager. If your team fits round one table, almost none of it applies. Four statuses, one priority field, fifteen minutes a week, and a list of what to skip.
Bug severity vs priority: what's the difference?
Severity is how badly a bug breaks the product. Priority is how soon you will fix it. They are set by different people for different reasons, a bug can be high in one and low in the other — and most small teams only need one of them.
What is a self-hosted bug tracker?
The term gets used as a synonym for "open source" or "free", which it isn't. What self-hosting actually means, what it buys you, what it genuinely costs you, and the cases where you should not do it.
Follow along by RSS.