Choosing a Bug Tracker

So now that Hudson is up and running well, it’s time to install an issue tracker for the new internal project.

  • What I really want to use but probably don’t have the budget for: Jira
  • What I might get the budget for but probably not: FogBugz
  • What I really, really don’t want to touch with a ten foot pole: Bugzilla
  • What I’m willing to touch with a ten foot pole if I have to: Trac

Anything else I should consider? Anything that passes the no-P.O. test that’s actually pleasant to use?

8 Responses to “Choosing a Bug Tracker”

  1. Paris Apostolopoulos Says:

    Hi there, I read your blog very often well done.Interesting points …very often!
    I was to a similar situation with you..having the same questions, until someone showed me Fly Spray!
    Really easy straight forward. its been a couple of months I use it..and I think its perfect, for issue tracking, to-do, bugs and whatever you want!

    Greetings from Athens

  2. Marco Hunsicker Says:

    Mantis might be worthwile to evaluate. Easy to setup, easy to use and feature-rich. Written in PHP under GPL. Integrates even with Mylar which makes for a nice workflow.

  3. Blake Winton Says:

    As a developer on DrProject, I feel compelled to mention it.

    It’s a fork of Trac, but seems easier to configure and use to me, and some of the new features it’s growing for the 2.0 (or maybe 2.1) release are looking pretty sweet.


  4. Augusto Says:

    Is integration with your CI tool (Hudson, great choice BTW) a requirement?

  5. Mark Mascolino Says:

    I’ve had decent luck with Mantis

  6. Chris W Says: is a ruby on rails based project management tool that has simple bug tracking and ties to SVN.

  7. Eric Says:

    Trac is excellent, and free to boot. Not sure if you really need the extras, but it also offers a lot more than just issue tracking (wiki, source browsing).

  8. Helge Richter Says:

    We’re using a modified version of Mantis as well and it works like a charm :)

Leave a Reply