Ideas, tutorials, and updates from our team.
A notification nobody acts on teaches people to ignore the next one. How we decided who hears about a task change in BugDump: recipients worked out from the task itself, nothing about your own edits, and a burst of triage clicks sent as one.
Custom fields are the feature every team asks for and then regrets. The test that separates a field worth adding from one that will be empty in six weeks, and the four that pay for themselves.
Every bug tracker ships low/medium/high/critical, and every team quietly renames them in their heads. What a priority scale is actually for, how many levels you need, and why the words have to be yours.
Most bug dashboards count things. The useful ones answer a single question: are we keeping up? Four metrics that do, the ones that quietly mislead, and a five-minute weekly review built on them.
A bug ID is not a database row number. It is a word people say to each other. Here is why per-project numbering and a short project key like BD-42 make a bug tracker easier to talk about, and the trade-offs behind the design.
Most teams are not slow at deciding which bugs matter — they are slow at everything around the deciding. A bug triage workflow that removes the navigation instead of asking you to think faster.
The design is in Slack, the log is on a drive, the spec is in someone's inbox. Why bug report attachments scatter across tools, what that costs when the bug comes back around, and how to keep every file on the bug itself.
Why heavyweight issue trackers fail small teams, what a lightweight bug tracking setup needs, and how to choose one that users will actually feed.