Robin Bowes said the following on 01/26/2006 07:50 PM: > I run trac for a client with several trac projects with a 1-2-1 relation > to svn repos (1 repo = 1 trac project). > > The main issue we have with it is the (lack of) the ability to produce > summaries across all projects (all oustanding tickets, all new tickets > this period, checkins this month, etc. etc.). > > So, from my perspective, if it was possible to create an "master" trac > project which could view all details from many "sub" trac projects then > I'd be happy.
I've been working with trac quite a bit over the last couple of days - new projects, modifying permissions, etc. This has given me a good idea of just what sort of improvements to trac would have made my job a lot easier. 1. Move users out of specific projects and administer them centrally, i.e. use RBAC to assign users/groups to specific projects. 2. Associate usernames with trac logins so it is possible to set them up centrally without requiring users to do it for each of their projects. Currently, if I create a project and add a user to the project then assign a ticket to that user, they will not get any email notifications until they login to trac and set their email address. 3. Make the reporting available centrally too, i.e. allow cross-project reporting. This too would be controlled by RBAC. Thoughts? R. _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
