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?<p>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!
We use Jira, but it is much more than a bug tracker. With Greenhopper, it offers us complete issue management, which includes iteration planning in stories and tasks. With FishEye it integrates a view on our subversion repositories into that, allowing crosslinks and beating the pants off of any other solution.<p>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.
We use GitHub Issues. It's very barebones but ties in very nicely with our source control site of choice: GitHub, and there is no need to context-switch.
YouTRACK--a keyboard-friendly fast fast FAST bug tracker from JetBrains (of IntelliJ fame).<p><a href="http://www.jetbrains.com/youtrack" rel="nofollow">http://www.jetbrains.com/youtrack</a><p>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.<p>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.<p>Edit: I see they are now offering a free hosted version for the first half of 2011.
I work for Atlassian so I'm biased ;)<p>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!
For those of you who don't know, the OP founded <a href="http://bugherd.com/" rel="nofollow">http://bugherd.com/</a><p>toast76, can you explain what makes BugHerd unique?
So I've been using "ditz" on a few projects and I quite like it. It's about the most minimal bug tracker you can get, but I like that the bugs get checked into your scm, right along with the code. I also like that I don't need to launch a browser to add or edit bugs. It fits in beautifully with distributed VCSes like darcs or git.
For musicbrainz.org we're using jira. I'm not particularly happy about that, mostly because jira is not open source/free software (and musicbrainz is). Otherwise no complaints, jira does everything we need it to do, and apart from some interaction design issues does it quite well.
We primarily use the GreenHopper plugin to interact with JIRA. This allows us to both track new development and defects in an agile friendly way, without the need to maintain all the index cards.
Emacs <a href="http://orgmode.org/" rel="nofollow">http://orgmode.org/</a>
in combination with
<a href="http://mercurial.selenic.com/" rel="nofollow">http://mercurial.selenic.com/</a>
Bugzilla. I wouldn't say I love or hate it, but it works and it's what I know. The biggest downside is that I'm not a Perl hacker, so if I wanted to hack on BZ, I'd have to take the time to learn Perl. Luckily I've never felt much of a need to modify Bugzilla. It just works.
I use Taskpaper as a task/bug tracking file.
Plain text file with GTD token support and line filtering.<p>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.<p><a href="http://www.hogbaysoftware.com/products/taskpaper" rel="nofollow">http://www.hogbaysoftware.com/products/taskpaper</a><p>I use an extended DarkMatterPlus* theme file from
<a href="http://groups.google.com/group/taskpaper/files" rel="nofollow">http://groups.google.com/group/taskpaper/files</a><p>* : @fix appear in bright orange, @cancelled behaves the same as @done etc...
Google Code -- I'm surprised it's not listed. I recently had to decide between GitHub's issue tracker (I'm already using GitHub for source code hosting) and Google Code, and almost everyone I could find that had an opinion said Google Code was much better.
I use <a href="http://www.codespaces.com" rel="nofollow">http://www.codespaces.com</a>, but I'm biased because I know the guy that founded and still runs it. It was the first app I saw that was fully written in Ext-js (this was pre 1.0) and back in 2007 or whenever it was that he wrote it it blew me away. It does all kinds of neat things, but mostly it's good because it's accessible to non-technical people -- lots of classic interface paradigms.<p>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.
We use Indefero <a href="http://www.indefero.net" rel="nofollow">http://www.indefero.net</a> It is both offered as free software (GPL) and you have hosting options. A bit like WordPress.
You should add an option to differntiate 'some other tracker' from 'a tracker I wrote myself'. I'd be interested to see how many hand-rolled solutions there are out there.
I voted lighthouse because that's what we use at Nowmov but for personal projects I use [Bugs Everywhere](<a href="http://bugseverywhere.org" rel="nofollow">http://bugseverywhere.org</a>) It's a simple command line tool that syncs to a file in your software's repo. Simple + Portable = LOVE.
I've used Flyspray <<a href="http://flyspray.org/>" rel="nofollow">http://flyspray.org/></a>; on a couple of projects with two other team members and it has worked well. It is php+mysql/postgresql, so it installs almost anywhere.
We use Bugzilla, but the non-techs in the company think it's too techy. Although it can get daunting with so many options, and I've even seen it used as a trouble ticketing system(!), it serves our purpose (bug tracking, of course).
I've got some stats on my site wappalyzer.com, I'll look into adding the ones you mentioned and aren't listed:<p><a href="http://wappalyzer.com/stats/cat/Issue%20trackers" rel="nofollow">http://wappalyzer.com/stats/cat/Issue%20trackers</a>
At ProjectLocker (<a href="http://www.projectlocker.com" rel="nofollow">http://www.projectlocker.com</a>) we use Trac for issue tracking for ourselves and as a hosted service. By extension, so do our customers :).
Lighthouse along with github's service hook has been great for me so far on a personal project.<p>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.
Mantis. Once I minimised most of the fields it looks fine. The easy of deployment is a point in its favour as well.<p>What I really want is a cut down JIRA written in PHP (for ease of deployment). If might just write it one day.
While I favor Redmine at the moment, I used Roundup in a previous job and didn't hate it. It does a pretty good job of balancing simplicity and features.<p>The only other place I've noticed Roundup being used is for Python.
Lighthouse FTW! Its lightweight, simple, easy for non-technical team members to use to report issues, bugs, suggestions, etc. and the tag-based classification/search system is inspired. Love it!
Email -> stop development and fix -> reply to email archive and hope you don't hear about this issue again. But looking into implementing FogBugz (or whatever recommendations come up)
a plain text TODO file within the repository of each project, together with a plain text TODO file in my dropbox that gets synced everywhere. Works very well.
Grooveshark uses Bugzilla. There are things about it we all absolutely hate, but it does the job, which is more than I can say for anything else we've tried.
redmine users may be interested in the recent fork: <a href="http://www.chiliproject.org" rel="nofollow">http://www.chiliproject.org</a><p>the forking devs are going to be comitting some more radical changes it seems
mtrack<p>a clone of trac done in php
With support for multiple projects.
Mercurial and Subversion<p><a href="http://mtrack.wezfurlong.org/" rel="nofollow">http://mtrack.wezfurlong.org/</a>
vi BUGS.txt<p>for as long as reasonable<p>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)<p>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