What bug-reporting tool do you use?

I just discovered FlySpray, which seems like a pretty nice tool for my needs. Especially the upcoming 0.99 release looks good. Since the latest stable release has a bunch of bugs and flow-problems..

Flyspray allows setting up multiple projects, versions, categories.. allows report-generation and can print out bug-dependency tree's (the upcoming release is supposed to do that using SVG !

One of the most popular tools out there seems to be BugZilla, which is pretty big in terms of features, but it's plain ugly and hard to get a good overview of what you are looking at at any given point, especially for non-developers.

So I'm wondering.. what tool do you use? Is there anything you can recommend?

Web mentions


  • gasperk


    We use Trac - it's quite nifty, a simple issue tracker with an integrated wiki and svn browser. Admittedly it's not _the_ tool for bug reporting if your userbase is big, but it has proved itself to be quite useful as a collaboration tool between the developers and the client for custom-made projects.
  • r)wley


    I suggest Trac ( for SCM - It has a wiki, source browser, ticket system etc. It has a handy Timeline and Road Map features as well.

    The beuty of it is that it can directly talk to the SVN repository and track live changesets that are linked to ticket ids and so on

    There are plenty of plugins - I use the Doxygen plugin for vewing API generated from source code.
  • Pierre


    I tested a couple of issues tracker, some even not in php. FlySpray is young but has the simplicity and the features I was looking for libgd. Other are either too simple (cvstrack :) or too complex (bugzilla) for my basic needs:

    - Multiple projects
    - Simple Roadmap definition
    - Custom flows (and step names)
    - user authentification can be required to post a bug
    - easy to extend (== relatively clean code base, mvc or not are irrelevant for me)

    The user side is very simple and easy to understand. The way it works is sometimes confusing but they are working hard to fix that before 1.0.0 (Thx judas_isc :)

    Check the result:

    My other choices were:
    - Eventum (too much install/update troubles, code base using PEAR and other things, but if you like that, it is a good one)

    - Mantis, I was looking for more flexibility in categories ordering or definition, mails, etc. I stoped after having had to enter the cats 5x ;)

    - FogBugz would have been my choice if it was opensource. This tracker matches nearly all my needs and requirements.
  • Evert



    I agree.. flyspray is also my choice, because its fairly easy to extend.. its PHP which is already a plus..

    I actually had a pretty hard time installing Trac.. I gave it a shot, but I simply gave up after a bunch of unsuccessful attempts..

    Also.. I'm kind of getting a feature overload there.. There's actually testers and project managers on our projects.. so simplicity is a must for me!

    Eventum and mantis actually look pretty nice! FogBugz looks even better, but I agree, the non-opensource thing is an issue :)

    Thanks for your comments
  • Oscar Merida

    Oscar Merida

    At work we've settled on Mantis, although I keep meaning to give Trac a shot now that I'm using SVN.

    Mantis has a good balance of features vs ease of use. There are some annoyances, like no email notification sent when a bug is assigned to you. And it is a big pain to have to enter categories each time for a project, but there is an option to copy categories from another project.
  • Marc Jakubowski

    Marc Jakubowski

    Take a look at:
    It has a really nice Design compared to the above mentioned.
  • Stefan


    I'm currently on the lookout. When I worked at TomTom, we used JIRA, which worked simply perfectly, but unfortunately, it's commercial software. Trac is a good one that I've been looking at for use here at my current job. But I'm going to have a look at the features of Flyspray as well. I haven't checked yet, but one of the most important features for me is SVN integration.
  • Derick Rethans

    Derick Rethans

    We're using wIT (it's not "free", but commercial open source) for our projects now, and it is simply excellent. Have a look around at our installation ( if you wish.
  • Adam Jones

    Adam Jones

    We use commercial Olate Arctic for our public bug/feature tracking because of it's nice interface and simple features. It's also very customisable both with the custom fields and the open source aspect.

    Internally we use Trac since it allows us to link issues with the source revisions. We mainly use this for tracking tasks that we don't want to make public.

    The main problem I had when finding an issue tracker was one that was simple and looked nice. We didn't want a load of extra stuff like provided in Mantis or Bugzilla (which isn't PHP) but wanted the base functionality we could build on. Arctic has let us do this. Trac is great because it syncs with SVN and that's very handy especially when you integrate it with the commit hooks in SVN.
  • Jan Schneider

    Jan Schneider

    Whups, of course . :-)
  • Benjamin Klaile

    Benjamin Klaile

    I can fully agree with "gasperk". We also use trac in our small web project.
    In my company we use mantis, due to the improved possibility to add notices within the ticket system.

    Though, I prefer trac because the SVN browser and the wiki are fully integrated by default.
  • dreamscape


    I use MySQL's Eventum.
  • Mike Willbanks

    Mike Willbanks

    bugs-bug-genie is not a very nice project. The design looks nice but the underlying code is a mess. It was very usable but when looking at the code to do any type of extension to it, it was as if having to hack something that was already hacked together.

    I have also used Flyspray and found that it gets the job done but hoping to see more functionality in the future.

    wIT is a great bug tracker. Something that if you don't mind dropping the money on is a great investment.
  • Hasin Hayder

    Hasin Hayder

    Flyspray is awesome. We modified it's core to meet our needs. But overall, its really cool.
  • MichaÅ‚


    The best one for me was always and remains Mantis:
  • Sebs


    As far as i did in a previous version review the sql ( a freind told me he had performance probs) flyspray aint good for a lot of error records ;).

    Bugtracking is often mission critical in some ways, so better look out in advance and do not have the pain of migration.
  • Greko

    Hi !

    Trac lovers, have a look at the new and exciting (imho) project Retrospectiva

    Sounds promising !
  • Thomas Koch

    Thomas Koch

    Have a list with links and german comments on:

    (And please add, if you still find others!)
  • Calisare


    maybe this blog will help you also:
    What tool to pick for bug tracking?(fogbugz vs trac vs jira vs bugzilla)
  • sminded

    We have been using Trac for almost a year and it works great. I would say the main benefits with Trac is:
    * Subversion integration
    * Possible to force ticket reference in comment when checking in source code via svn pre-commit hooks.
    * Simple yet elegant UI
    * Plugin architecture allows others to make good plugins. There are tons of them out there, some of which are actually quite good.
    * Integrated WIKI
    * Integrated Source browser
    * Changeset feature allowing you to see what actually changed in the source code for a particular ticket.

    The Retrospectiva project seems promising, its basically a remake of Trac using the ruby on rails framework, and adding some interesting features like Blog support. Nice!
  • imran


    plz tell me how can i solve the synchronous email sending in notification b/c there is a problem in which page is still after the whole mails will not forward to the desired person help me