On Thursday, June 26, 2014 11:10:48 PM UTC-7, RjOllos wrote: > > > On Jun 27, 2014 1:00 PM, "Maba" <cold...@gmail.com> wrote: > > > > Why not go with several projects? > > It does not sound as though customers map 1:1 to projects. > > Anyway, the same question was posted on the Bloodhound mailing list and > we suggested a custom permission policy (or TracFineGrainedPermissions if > appropriate). >
PrivateTicketsPlugin also supports the scenario you are describing, but it has performance issues: http://trac-hacks.org/wiki/PrivateTicketsPlugin A simple permissions policy would take the authenticated user and ticket reporter and determine if they are members of the same group before deciding to grant view access to a ticket. You'd have to exclude or remove groups that everyone belongs to such as //anonymous// and //authenticated//. I hope to eventually add a sample plugin to Trac that demonstrates the behavior since it seems to be requested fairly often. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
