David Abrahams wrote:
However, I anticipate a problem with ticket and milestone management.
Thes data are not shared across Tracs in the same way that the SVN
repository is, so IIUC there will be no easy way to get a report of
all the most urgent outstanding tasks, across projects, or get a
report of all the tasks that are assigned to me, or find out which
milestones are coming due next.
Correct.
Of course if I put everything in the
same Trac, I can get those reports, but then IIUC I can't easily
control client access to the wiki pages, tickets, and milestones that
they're supposed to see and modify.
Also correct
Has anyone thought about this?
Lots of people have
> Is there a solution out there already?
Kind of. If you use trunk, and PostgreSQL, then you can put each
"client" in a separate PostgreSQL schema, instead of database. This
will make it easier to write a custom report, as querying across schemas
is possible.
The other option is to use the security sandbox [1][2][3]. It will give
you finer grained permissions, though I think it is largely untested
beyond alect the developer.
Additionally, there have been various discussions about multiple project
support in a single environment, etc. All that has really been decided
is that it's a >1.0 feature.
HTH
-John
[1] http://projects.edgewall.com/trac/wiki/PermissionPolicy
[2] http://lists.edgewall.com/archive/trac-dev/2006-May/000487.html
[3] http://svn.edgewall.com/repos/trac/sandbox/security/
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
