Authorization

As you, all knew we shifted from Trac to Redmine for project management (issue/ticket tracking, source control management, mileposts). I am egger to tell few revealing facts experience at Redmine comparatively to th at of Trac setup my previous location.
I have concluded from the Trac mailing list and further discussion on the comments by some core developer is that the prime objective of Trac is to generate or build a basic static or groundling an extendable with the use of plug-in, which is a supreme mission statement. It poses but in it, as if once you are managing numerous Trac installations at a time, this scope turn out to be against you in an agile manner, though I miss few important things in Trac.
MULTIPLE PROJECTS
The initial ground for moving to Redmine was of the lacking sustained for multiple projects at Trac. I am sure you can hack Trac (see track- hacks) to let in multi project support, but still I do not prefer hacking. There were various discussion how (and if) Trac should enforce multi-project support concept: there lies no “out-of-the-box” resolution. I study something about Trac v2.0 supporting this, so I may suppose we will find that in around 2015 or so.
Whereas best thing about Redmine is, it does affirm multiple projects. The desegregation throughout the entire system is top-drawer. It allows you to create nuzzled subprojects and move issues/tickets from one to another project. Even for each project, one is free to assign different users and turn a few functionality (milestones, source control, time tracking) on and off which is additional icing to the sugar.




