31–40 of 45 posts
I'd also recommend Pivotal Tracker. Its simple, neat, and gets the work done.
We use Pivotal Tracker to manage all our development projects. It's not only a bugtracker, but extremely usefull if you have any kind of agile process.
I'd also recommend Pivotal Tracker. Its simple, neat, and gets the work done.
I hate Pivotal Tracker. I've been forced to use it on a few projects and found it way too hard to use. E.g. it never shows what you're working on by default and you have to open up a special window for it. And you can't just mark something as done - you have to move it through a whole set of crazy states like accepted and delivered. I'd much rather use any other bug tracker or something simple like a spreadsheet.
GitHub has just enough issue tracking tools for my needs.
We use Lighthouse http://lighthouseapp.com/ We needed a simple tool which can also be used by people who have minimal computer knowledge...
I'd also recommend Pivotal Tracker. Its simple, neat, and gets the work done.
I think generally if you want to second someone's recommendation, it's best to upvote their recommendation and add your comment as a reply - otherwise, the votes get fragmented between the two recommendations and if a person comes to the post and just scans the top comments, might not even see either of them.
Earlier quoted context omitted.
I think generally if you want to second someone's recommendation, it's best to upvote their recommendation and add your comment as a reply - otherwise, the votes get fragmented between the two recommendations and if a person comes to the post and just scans the top comments, might not even see either of them.
Sure. But the other comment was posted during the time when I was composing mine. So I didn't get to see it until I submitted my post.
I absolutely love Fogbugz. I find Jira to be a bloated, complex mess. I've also used Trac and Bugzilla, both were clunky and lacking in creature comforts.
It's the best bug tracker around. The only downside is that it is so configurable people will start using it or non-bug tracking things, which doesn't work well
We integrated it extensively with Subversion a few years ago, and there already exist pre-built Git integration modules for it. The plugin ecosystem has come a long way.
One important criteria to me personally was the suitability of it for use as a project management and/or feature roadmapping system, not just an actual _bug_ tracker per se, explicitly for bugs in the sense of defects. Mantis performs extremely well on this count as well.
Probably the biggest high-profile use of Mantis I know is Digium's issue tracker for Asterisk: http://issues.asterisk.org/ -- you can see it in action there. Their particular use of it relies on Mantis's extensive ACL features (optional--you don't have to get that complicated if you don't want to!) to open the process of enrollment and bug submission to the public at large, to allow certain people intermediate levels of access (e.g. QA testers), and to impose an actual hierarchy of developers, managers and bug marshals inside the company.