Product decisions, engineering field notes, and the bets we're not planning to revisit. Written by the people who ship Bugspot.
RSS feedSeverity measures a bug's impact; priority measures when you'll deal with it relative to everything else. They're independent — here's the difference, a 2×2 matrix with worked examples, and who sets which.
A bug tracker is the system of record for defects in your software. But almost no team runs a bug-only tool — and the reason why says a lot about what you actually need: not a bug tracker, but a way to manage the whole development process.
What separates a bug report that an engineer can act on from one that bounces back with "cannot reproduce" — plus a copy-paste template you can use today.
The shape of Bugspot, why it exists, and the bets we are not planning to revisit.
Where we draw the line on workflow configuration and why.
Why we declined custom fields, the recurring pain they cause in trackers like Jira, and the adjacent pitfall — labels — we avoid for the same reason.
A note on why I am building this, who it is for, and what to expect from the blog.
What we shipped, what we ripped out, and the metric we watched too closely. No drip campaigns, no "is your team ready for AI?" — just the post.
Free during the public beta. Ten minutes to set up a project and move your first entry across the board.