Jason,I used to think of using multiple trac, but eventually found out that it is all about the structure you choose. Naturally I cannot know the nature of your problem, but I suspect that a restructuring of the way tickets, milestones, components and versions will obsolete your need of multiple repositories. Feel free to mail me if you want to know how I structured our development.
I am trying to maintain a blog about this at: http://tandem- method.blogspot.com. Any feed back is most welcome.
Finally I want to stress the usefulness of RSS-feed from trac. We use it extensively to make sure everyone is on top of their tickets. Remember that you can add parameters to a report (View tickets) when you set up your RSS-feed.
Example: http://trac/cgi-bin/trac.cgi/report/1?format=rss&USER=jason Kind regards, Philip Bergen On Jun 13, 2006, at 9:54 PM, Jason Harrison wrote:
I have tried to find this feature in the Trac ticket/feature requests list as well as in the archives of the mailing list. It does not seem to exist.Because of the design of Trac, we are using several parallel Trac projects for our development projects and todo lists. Thus it is very easily possible for members of our team to forget about a ticket on a project that is not being monitored closely enough.Is it possible to general a weekly report of open tickets for all (or any) Trac project and then email it to a general mailing list? Is it possible to do this on the server, or within Trac itself? I would consider using something like curl or lynx to scrape the report out of the webserver and to clean it up a bit. But is should be possible to pull the content we need out of the SQL lite databases for the projects, sort it by owners and then distribute it to the group or individuals.Has anyone done this kind of reporting before with Trac? Hints? Pointers? Code?
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
