Live data from Hacker News

Poll: What's your favorite bug tracker?

news.ycombinator.com

31–40 of 73 posts

Re: Poll: What's your favorite bug tracker?

#31
post #16

asana

How do you use Asana for bug-tracking? We're considering doing so too (We already use Asana for task management, etc), and would love some pointers from someone who's already done so.

They have a guide (http://asana.com/guide/videos/bug-tracking) in their help pages about it. I use it too, but not their way. I don’t have a “Bugs” project. I have a “Bug” tag that set to bugs in different projects. If you already have a projects structure that works for you and can hold issues like bugs, this might work better.

Re: Poll: What's your favorite bug tracker?

#32

Earlier quoted context omitted.

How do you use Asana for bug-tracking? We're considering doing so too (We already use Asana for task management, etc), and would love some pointers from someone who's already done so.

They have a guide ( http://asana.com/guide/videos/bug-tracking ) in their help pages about it. I use it too, but not their way. I don’t have a “Bugs” project. I have a “Bug” tag that set to bugs in different projects. If you already have a projects structure that works for you and can hold issues like bugs, this might work better.

We use asana as a bug-tracker at https://circleci.com. Its pretty good, and doesn't get in your way, but we can't really integrate it into our workflow. They don't have Hipchat integration, and their API isn't full enough to set it up ourselves with Zapier.Their support also isn't very good, they replied to the problem with basically "dont care".

Re: Poll: What's your favorite bug tracker?

#33
post #2

Jira.

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).

Re: Poll: What's your favorite bug tracker?

#34
YouTrack (http://www.jetbrains.com/youtrack/index.jsp) is my favourite out of everything I've ever seriously used. Physical cards stuck to the wall also works well for small, co-located teams.

The important things are that someone needs to put a decent amount of time into managing the bug list, and you need to be actually willing to devote appropriate resources to fixing them (or better still, eliminating the root causes). If those aren't present you'll just end up with an unmanageable dumping ground regardless of where it lives.

Re: Poll: What's your favorite bug tracker?

#36
post #12

I'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 its own problems.

GitHub (once you get past the signup) is perfect in this regard. Just open a ticket and then comment on it.

I wish GitHub had more in regards to bug tracking, for example being able to create states (open, in progress, closed) as well as labels.

These days I'm sure there are comparable solutions but having the issue system through github means one less service I need to track, which is also nice (client gets code, client has issue tracking, done).

With all that said I wouldn't use github issue tracking for complex multi-stage applications where the environment is an important factor in the problem.

Re: Poll: What's your favorite bug tracker?

#38
post #6

Earlier quoted context omitted.

Surprised its not on there. FWIW here's a list of major issue trackers from Wikipedia: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_sy... .

Any guesses as to how Jira got left off? In my exp it's one of the most popular issue trackers & integrates with other PM tools.

I'll tell you exactly how it got left off.

I've just never heard of it.

Do most HN readers have the impression that polls like this are made by some some all-knowing, perfectly fair, professional editor who only puts up well researched, carefully thought out, scientific and objective options in their polls?

It might surprise you, but I'm just another HN reader just like yourself.

I woke up today and thought, "Hey, I'd like to know what other HN readers consider good bugtrackers. Why don't I put up a poll?"

I remembered the names of a few of bugtrackers off the top of my head, but just having a few would make for a pretty lame poll. So I pulled up the wikipedia article on the comparison of bug trackers. It had a million listed, so I thought that might make for too long a poll. So I chose the ones I personally heard of, and added an "Other" category for the rest.

I hope that clears up some of the mystery.

Re: Poll: What's your favorite bug tracker?

#39
post #2

Jira.

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).

I'm surprised. Our company evaluated several bugtrackers and jira was by far the best. We're still using it two years later and still quite happy with it.

Re: Poll: What's your favorite bug tracker?

#40
post #19

Other. Write code without bugs. (I say this in jest, but only a little.) Think about it... I know so many programmers who get lazy because they have such good debugging tools (Let me just slam something out there and let the debugger catch it.) I hate this. If we developers would slow down and think a little more about what we're building, we may find a dramatically decreased need for debugging. Variable local or glo…

Bugs are inevitable. No matter how much you think about the problem, there will always be things that slip between the cracks.

This is true, but you should probably still put more emphasis on avoiding them than optimising your process for fixing them.
Post reply on HN