Yet another post to add to my “Ask The Readers” cycle. What are you guys using for bug/issue tracking. As we all know, there are 3 things that distinguish a real software developer from a ‘just out of school’ newbie. These things are (not necessarily in that order):
- Real Programmers use Source Control
- Real Programmers Track Bugs
- Real Programmers use Emacs and/or Vi
Yeah, you thought that #3 would be about documentation or Unit testing, but it’s not. I’m feeling subversive and mischievous today (after all it’s April first) so you get the Vi/Emacs remark. Deal with it.
It’s easy to pick source control, since after all there are essentially only two worthwhile systems out there: cvs and subversion. There are some other systems that offer cool features, and I’d love to hear why your system is better than the others, but at the end of the day these are the two important ones. They are basic, simple and powerful.
Bug tracking on the other hand is a whole different animal. There are dozens of systems out there, one more bloated than the other. Personally I use a home grown system which I dubbed SITS, and which is my little vaporware project which may or may not become public at one point. It is very basic, and simplistic – not to say primitive. For some time now I have been looking around for alternatives to see if perhaps there is a more organized, polished way of doing these things. So far I haven’t found anything that would suit my needs. So I figured I might as well ask here. What do you use to track your bugs?
I’m really looking for something simple, preferably web based, and if possible something that could work as an issue tracking system as well so that I could keep my syadmin tasks in the same place as software related bug reports. PHP+Mysql is proffered since this is the platform I’m working with, but I’m open to new things.
Suggestions? Let me know what works for you, what doesn’t and which systems do you hate.
[tags]bug tracking, issue tracking, sits[/tags]