Bug Tracking for Small Teams

Every project needs a bug tracker, and let’s face it, there are plenty to choose from. Problem is, small teams don’t need or want hand-holding and every feature under the sun. Just a straight-forward, light weight system for managing actionable tickets. Bugrocket is something for the little guys.

There are no due dates or time estimates, no ‘default assignee’ (well, there is, it’s you), no ‘companies’, no complicated access permissions, no custom fields and no graphs in sight. That’s all unnecessary if you’re practically sitting next to each other or are an IM away. There’s no need for a bunch of rules or attempts to make sure you don’t ‘forget’ or ‘miss’ tickets, no one on your team is trying to sweep things under the rug. You know which release you’re on, which deploy is coming up and what goes where because you talk to each other.

Of course, Bugrocket tickets do have some properties: title, status + priority, tags (only used as visual cues), which release it’s supposed to go in and who it currently belongs to. For a given release you get a little blob of markdown at the top to describe it and an insanely simple filtering UI that acts instantly on the list of tickets and… well… that’s really it. If you can’t describe a feature in less than a single sentence, Bugrocket probably doesn’t have it.

Forget about wiki’s (you have one already), elaborate email integration, customer support and source code repository management (one size doesn’t fit all). Tools with all these things force you into a way of working that don’t fit 100% and end up just getting in your way.

When it comes down to it, bug tracking is something that happens all day, every day - it needs to be low-barrier and low-friction. You have a small team, maybe even just you and a friend, and you need a bug tracker – you have lots of options, but nothing meant just for you and nothing as simple as Bugrocket.