Trac

Testament to success:

I started my current job 1 1/2 years ago. When I started everybody had to use bugzilla/CVS. I setup trac/svn for my own use.
Today nobody uses bugzilla anymore, and only a few still use CVS, the rest has gone over to trac/svn and has been happy ever since.

What better testament can there be?

Trac is excelent because:
* it has a wiki
* it has a timeline of activity
* it has issue tracking
* every entry field allows wiki syntax
* you can link from anywhere to anywhere simply
* it has a source browser
* it has milestone management

It has greatly reduced the amount of mail send around and greatly structured communication and development for us. Our customers also access the Trac and file tickets there.

Trac is an excellent integrated tool when it comes to browse the source code, create wiki pages and manage a few hundreds or thousands bugs. But forget it if you plan to use it primarily as a bug tracking tool for a very big project. The DB model used for bug tracking is quite simplistic and does not provide advanced functions like bug dependencies, "duplicate of",...

Say goodbye to overbloated crap like MS Project. Trac provides just enough project management as you should need. In other words, they don't impose or require a bunch of un-natural hand-holding and busy work like "what percentage of this feature are you done with?". I hate those kinds of apps. No real developer tracks their "sprints" or features on an hourly basis.

Trac integrates milestones, wiki, code repository and defects better than anyone else. Any multi-person project that doesn't use it should have their head examined.

My only nitpick: no built-in Git support.

I've had to fight with ticket and source viewing systems in the past but Trac does it wonderfully. It is true that it's bug tracking is not as detailed as bugzilla or some other bug trackers but it gets the job done. The community around Trac has posted up many plugins, patches, macros and hacks that (can) make Trac fit what you want even more.

It's light weight, simple to administer, and easy to use!

I introduced trac in a scientific software development environment. In a very short time it was well accepted even by non developers. One strength of trac is the integration of ticketing, scm, and wiki with one intuitive ui.

The other strength of trac lies in the numerous plugins which add a lot of useful features to the trac core like calendar, blogging, source code review other scm than svn, tags, forums to name a few.

Trac is really light and the fact that you can use it without a server is really cool. Though Trac may not be for big projects which need more advanced features, its perfect for smaller projects going to about a million LOC. I myself am quite new to using tracking tools and stuff. Trac is excellent for people like me because of its spartan nature, excellent documentation provided as part of the setup and for use on lone developer personal systems. If you are a lone developer, there is nothing better.

Trac is a very nice tool to manage any project you do.

You have the wiki, sourceview, bug list, user management, milestones, reports fearture in one tool.

I use it to manage my projects.
With it you are able to create your Wiki, documentation and notes to your source code within minutes. Everything you need is there.

The only disadvantage is that you can't install it on a ordinary webhoster.
But you don't need multiple software to manage your project.

The best part of trac is the incredible community. There are literally 100s of plugins that can extend trac. The irc channel and mailing lists are always active. Trac is basically a plugin framework and very easily extendable. If plain trac doesn't work for you, try some plugins from trac-hacks.

great product

Thank you so much. Nothing else to say.