I just want to mention that Trac development has picked up steam over the last couple of years. If it has been a while since you've tried it, you might give it a fresh look sometime.
Poll: What's your favorite bug tracker?
41–50 of 73 posts
Re: Poll: What's your favorite bug tracker?
#42Conductor (http://conductor-app.com) is my current favourite.
Re: Poll: What's your favorite bug tracker?
#43Hi, I'm Joe Stump CEO/founder of Sprint.ly. Totally biased opinion here, but I'd like to add Sprint.ly to the list. We built Sprint.ly specifically to encourage/engage "the rest of the business". If you're looking for a super technical tool, we're not that, but if you need a tool to get business users engaged and on the same page we might be worth a look.
Re: Poll: What's your favorite bug tracker?
#44For client projects I'm a big fan of Lighthouse (https://lighthouseapp.com/). It has a great balance of advanced features and ease of use for non-techies.
* Tickets can be created and updated via email
* Using the GitHub service hook, you can tag commit messages so that they appear as comments on a ticket as well as change the state of the ticket (For example: "Refactor widget behaviour [#123 state:resolved]")
* You can setup milestones (with or without a due date) and assign tickets to them
* Bulk editing of tickets
* Markdown in ticket description and comment fields
* You can easily create "buckets" of tickets based on search terms and filters
* Bugsnag and Airbrake can be configured to automatically create tickets for new exceptions in your app
* Probably some other great features that I've forgotten to mention
Re: Poll: What's your favorite bug tracker?
#45Jira.
Makes me wonder how some polls would turn out if options had both upvote and downvote buttons. I have used every bug tracker in this poll, as well as a few more (redmine, Assembla, GNATS, OTRS, Roundup, ikiwiki, various custom internal tools), and Jira was by far the second worst (behind one of the custom one-offs).
[deleted]
Re: Poll: What's your favorite bug tracker?
#46Good old Rake with the # FIXME directive right in my source code.
Re: Poll: What's your favorite bug tracker?
#47I'm surprised GitHub is by far #1. I wonder if it's familiarity rather than preference. Github's minimal approach of using labels for everything is like Gmail's tags over folders. I wish GitHub had a "This bug affects me" or +1 button so the comment history stays clean of "me too" responses.
I also feel such a questionaire is mostly driven by experience not by preference. Not many people learn to know more then 2 or 3 trackers in their career.
I question whether people need to learn more than 2 or 3 trackers over a career. Bug tracking tools are remarkably well developed. Once you find something that works, start battering bigger fish.
Re: Poll: What's your favorite bug tracker?
#48Fossil (from D. Richard Hipp, SQLite author)
Re: Poll: What's your favorite bug tracker?
#49I'm surprised GitHub is by far #1. I wonder if it's familiarity rather than preference. Github's minimal approach of using labels for everything is like Gmail's tags over folders. I wish GitHub had a "This bug affects me" or +1 button so the comment history stays clean of "me too" responses.
I've used a ton of bugtrackers, GitHub is the only one I've been able to hand to a non-techy client so they can create bugs. This has been a huge frustration for me when it comes to bug tracking. I have multiple clients who just aren't technical people and when they see the wall of options that bugzilla and mantis offer it causes them to give up and email me directly. I even tried vbulletin for awhile, but that had i…
I know mozilla has a drastically simplified interface for reporting Firefox bugs. Is that not an option in general bugzilla installations?
Re: Poll: What's your favorite bug tracker?
#50Earlier quoted context omitted.
I also feel such a questionaire is mostly driven by experience not by preference. Not many people learn to know more then 2 or 3 trackers in their career.
I question whether people need to learn more than 2 or 3 trackers over a career. Bug tracking tools are remarkably well developed. Once you find something that works, start battering bigger fish.
That attitude doesn't work for open source projects, where you need to worry about any barrier to pulling in new contributors.