Bunzilla is a bug tracker I made for a project whose plans and notes were becoming too numerous and unruly to manage effectively with pen and paper... (Read More)
All of the bug tracking solutions I had found seemed to have been designed sometime in the mid-90's for large teams of developers in a stifling and/or corporate atmosphere. Their concept of bug tracking was all about toiling away in an unending rat-race of sheer drudgery just to see who can claim to have "resolved" the most tickets in the least amount of time.
This of course led to a not insignificant amount of issues being
**MARKED AS DUPLICATE**and consequently
**CLOSED — YOU MAY NOT REPLY**, if you were lucky enough to notice that among all the needlessly verbose meta-data and fixed-width monospace eyesore, you might start to wonder if you had wandered into a forum moderated by children with fragile egos, or if developers were shot on sight for not meeting some sort of daily "resolved" issue quota.
I needed to keep my notes private, so public solutions like Github were out of the question, and I wasn't about to pay for the privilege of writing down my own thoughts.
I remembered an approach one of my early mentors had in developing a forum. He would make topics consisting of short, oftentimes incoherent, clearly frustrated messages and reply to himself to keep track of everything that needed to be done.
I decided to adopt a positive, can-do approach geared towards small teams of developers (read: just me) that had the same set of features necessary for a bug tracker with none of the formality (or drama).
It's on github and I'm hosting a live demo. I also wrote some documentation, linked below. Bunzilla is still very much in development, but it's reached a point where it does what I originally intended it for, so I've focused my attention back on my main project.
This project has really helped me get my chops honed again after a long haitus from coding. Structurally, it's very similar to a forum, blog, or other simple CMS and honestly I can't understand why other bug trackers don't just embrace a simplistic, open-ended, content-focused approach.