3 ms·
I actually used to develop on a bug tracking system. I've used dozens. I've never found one that was any good, and the majority of engineers and managers alway
by thorax 19y ago
I actually used to develop on a bug tracking system. I've used dozens.
I've never found one that was any good, and the majority of engineers and managers always complained about them. Either they're slow, unwieldy, complicated, feature light, bad at reporting, don't integrate with source control, integrate too much with source control, etc.
I have a cynical view about them now and pretty much put-up with whatever I have. Since I know they're all pretty bad and it's impossible to please everyone, my expectations have been lowered.
Someone who used to also develop on bug tracking software told me to check out JIRA, but I'm skeptical as always:
http://www.atlassian.com/software/jira/ http://www.atlassian.com/software/jira/
- cstejerean 19y agoI'm not very pleased with Jira. We've had constant issues with it being slow or going down. Jira has a lot of features but most of the time it gets in my way. The good news about JIRA is it has a decent API so you can probably write your own tools and reporting on top and not have to put up with their crap UI.
- wallflower 19y agoI like Jira. We use it to track pre-release software defects and it is quick to do commonly used functions like searching, screenshots, commenting on issues (no, it doesn't integrate with our CVS but we don't need it to). Once the software is released, per protocol, an issue with the software has to be tracked through our Siebel CRM solution (ugh, ugh). Jira compared to Siebel in terms of developer friendliness/usability - no contest.