Hi,

I'm developing a web application for the company I work for. We now need a bug tracking system, and I'm trying to decide between Mantis and Trac.
I've used mantis for over a year, and it worked fine, but Trac looks great.

Which one would you recommend?

Thanks,



Matias.

Because of its popularity, I would recommend Bugzilla.

However, you don't indicate your requirements, so any recommendation would be difficult.

Well... after more and more investigation, I think i'm going to use mantis:

Due that,

* it's already translatd to spanish (our language). Trac will be in a future version.
* it has a user registration/authentication/authorization system. The one for Trac is too basic.
* it works with mysql, that we also use for our app, so I don't have to install anithing else.

Cons:
* Due thar our production server, is on our intranet, it doesn't has a mta running on it, so I wonder if is possible to set up mantis to run with an external smtp server. Our production server has FreeBSD.
* It doesn't has a wiki or something like that, but we have already a wiki in another server, so we could just link to it from mantis.

Thanks.

We are also testing trac. The reason you choose to evaluate trac, is beacause it provides a wiki, a issue tracking system, it can generate reports and supports svn.

Here are our main problems now :
* Multilingual interface
Trac doesn't seem to have catalogs, at least the version i tried to add easily (ie. via property,configuration files) translations for other languages. So i would have en_US.properties or any extensions the file has to have, fr_FR.properties, and so on.

* Easy multiproject support
I would have liked trac being able to support multiprojects without any plugins or libraries : You have a main structure(in programming language) and that structure can contain one or many projects. The relationships can be obtained via a database query or a filesystem.

*Trac doesn't have built-in authentication system.
You can support authentication via apache htpasswd and configure httpd.conf/apache2.conf or use htdigest .

Once again this could have been handled in a database or in a simple configuration file. A redirection to a login page could have be done via a handler if there is no session key or no cookie. In the database the security could have been organized with the unix concept of groups : A group contains users which have some permissions.

The bug report interface could have been easily customizable
it can be customized by adding or removing fields now. Actually, If you want to remove fields, you have to mess with the trac templates where everything is hardcoded... Again the default displayable fields could have been stored in a configuration file, where you could choose to hide one ore more of them.

BTW, Bugzilla has a poor interface, real ugly. It is not good for use with novice users or users who are not developers. The interface and the logic behind bugzilla are confusing.

Yes, for all of this, iit think that a combination of mantis+dokuwiki could do the task better.