BATCH ISSUE/TICKET EDITING

I have to agree Trac ticketing system is very powerful and flexible. Without a doubt Trac is one of the most common and stable tools for online project management & issue tracking for a very good reason. You can easily search and filter tickets by severity, project component, version or owner, and then store those. Great.

What i really miss using Trac is the ability to do a “mass update” (edit/close/move) on several tickets at the same time. This is where the ajax powered “batch edit” feature of Redmine comes in quite handy.

USER / ROLE MANAGEMENT

The user management in Redmine is great ! Besides normal user management it supports (custom) roles. You are able to set different user roles for different projects.

Trac doesn’t support “user management” out-of-the-box. Unlike other bug-tracking systems that simply have a table for storing the users, Trac took the approach of allowing users to leverage the numerous authentication modules available for their web server. This means system administrators are able to hook Trac into something like LDAP, Active Directory, or whatever centralized user system that they already have in place.

So which one is better? Difficult question. I am a great supporter of working software out of the box. Not too much configuration, easy to install. This doesn’t mean the software has to be “simple” : flexible and easy-to-configure can go along hand in hand. That being said i think Redmine took the best approach in having good user management right after installation. If you need something more centralized they still have LDAP support.

Few Additional Features

Well, its certain Trac is much more stable than that of Redmine. Therefore, if you necessitate a stable product, Trac is better. However, as far as a minor web design company like ours is concern, the stability of the maturation environment is not actually that decisive to us.

Now what we aspire for in, online project management software is innovative features/plans to improve the way our squad is operating together. I frequently monitor the Red mine timeline / activity to observe how other people are utilizing the Redmine platform. Though many of their reviews/ideas inspire us to alter the way we are functioning or initiate applying a particular feature yet we have not paid enough attention.

Shall we see for more?

However, every coin has two sides similar is the case with Trac. Trace has a vast community with a multiple core developers, while in Redmine has a restricted access build around with few person involved. The source repository browser in Trac is comparatively more herculean and visceral.

Now since I am working along Trac for a long time and hence posses a great deal of regard for the hard work of all the people associated on projects.

Still as discussed earlier the Trac strength is also its impuissance somewhere. The key is to maintain the system less accented as it can be, other prime features does not sound worth for core decision making at the end.
[via www.digitalbase.eu]