Poll: What do you use to track your bugs?
What tools do fellow hackers use to track their bugs, issues, features and client/user feedback. Do you like it or hate it? If you don't use one, why not?
EDIT: As some of you may know, we're building a bug tracking tool of sorts (actually something a lot different to all the tools listed). The point of this poll is to find out what folks like us are currently using. Your input would be greatly appreciated!
(
74 comments
| 49 points
| on HN
)
We switched to Jira after getting annoyed at Mantis once too often. We all had experience with Bugzilla, which is like using bow and arrow in these days of guns. We investigated for a bit, looked at Trac and FogBugz amongst others, but decided in favor of Jira, primarily because of Greenhopper. Issue management without decent planning abilities is like a blunt knife: usable, but unnecessarily hard. Haven't regretted it one single bit.
It does take time to get setup to fit your organization but it has been worth it.
http://www.jetbrains.com/youtrack
After I gave up the concept of tracking bugs and doing feature planning in the same app (sounds great but has never worked in practice), this tracker became my default for any projects where I have a say in the matter.
We moved from JIRA because administering a JIRA installation is practically a full-time job. Have also used Fogbugz, Redmine, Mantis, Bugzilla over the years, so that list is my main basis for comparison. I hate YouTRACK less than those.
Edit: I see they are now offering a free hosted version for the first half of 2011.
Especially when all the notes are on a public window/wall. This way everyone can see the 'queue' of stuff and is a good reminder to re-prioritize constantly.
Good to see another Australian company taking on the software development market. Especially good to see that the company is partially funded by the Atlassian founders!
Not so sure if we fall into the software dev category so much as the web dev category as we're really only supporting tracking on websites and web apps.
toast76, can you explain what makes BugHerd unique?
BugHerd is a tracker for web developers and designers run within the website you're working on. Part feedback tool, part bug tracker, part QA tool. It's a bug tracker that engineers, designers, clients and stakeholders can all use. Each group has a different interface meaning no one is ever in over their head. A lot of the stuff you normally have to enter manually is logged/tracked automagically, meaning more often than not a short description is enough to get all the detail you need to reproduce a problem.
When a user goes to look at that bug, they're taken to the actual page and location where the problem occurred. This means that even as the page changes our bug tagging still points to the right place.
We also keep tabs on all sorts of user/browser information to ensure a bug can be replicated. We have some more tricks up our sleeve for replicating page state and user data (not yet released).
Clicking at the beginning of '-' prefixed line will add @done(2011-02-22) and appear as stricken through, and even hidden or moved to the end of the file. I have one per project, and they are tracked with git. Searching for "not @done and not @cancelled" will only leave the tasks remaining to be done.
http://www.hogbaysoftware.com/products/taskpaper
I use an extended DarkMatterPlus* theme file from http://groups.google.com/group/taskpaper/files
* : @fix appear in bright orange, @cancelled behaves the same as @done etc...
http://www.atlassian.com/software/jira/hosted/
If everything goes to plan, there'll be an announcement at Atlassian Summit (in June) that you might be interested in:
http://summit.atlassian.com/
I also voted for Trac, because that's my go-to bug tracker for corporate projects that get checked in to a private SVN server.
NOTE: I ""SUPER-HATE"" it. But I am helpless. :(
http://wappalyzer.com/stats/cat/Issue%20trackers
On a related note, why can't we have public bug tracking on a private repo on github? This was the primary reason I went with Lighthouse.
What I really want is a cut down JIRA written in PHP (for ease of deployment). If might just write it one day.
The only other place I've noticed Roundup being used is for Python.
Do you have a formal-ish system for this? Notice issue -> TODO -> write unit test -> fix issue -> cut + paste to ChangeLog?
It's mostly: email to say bugs need fixing -> bugs get fixed -> fix gets committed and the bug removed from the todo -> email back that it's fixed.
It mostly concerns visual (html/css/templating) bugs or small js bugs that don't have unit tests/
Request Tracker by Best Practical is an amazingly flexible product, straightforward, yet easily tweaked into whatever workflow most any organization could need.
That said, we use TRAC for software project management and project-based issue tracking.
the forking devs are going to be comitting some more radical changes it seems
a clone of trac done in php With support for multiple projects. Mercurial and Subversion
http://mtrack.wezfurlong.org/
for as long as reasonable
thought that file's length should be 0 (for as long as reasonable, and even then, should only be due to bizarre/unreproduceable platform causes, not a direct flaw in your application source)
yes this system works best if 1 programmer. but 1 programmer is the ideal team size, if you can achieve it for a particular project