2008/7/26 Mcgill Guy <[EMAIL PROTECTED]>: > > I dont think trac support per object permissions, it's more fine > grained to defining permissions on all tickets. trac in general has a
Internally Trac does support per-object permissions and the authz_policy provides a relatively easy way to apply them. > very nice permission system. it's not however its biggest asset. its > biggest asset in my view is the plugin architecture that allows you to > build plugins to almost do anything. > > On Jul 24, 9:47 am, Sergey Petrov <[EMAIL PROTECTED]> > wrote: >> I've got particular need that I cannot believe isnt common. >> >> I want to be able to customize view permissions for any ticket. When I >> create new ticket I want to be able to enter list of users that will >> have ability to view this ticket (or choose total visibility). If user >> is not in that list — he shouldnt see ticket even in query result >> lists. This can be achieved, but you'd definitely need to write a plugin. >> >> So I need: >> >> 1) Ability for any user to create tickets that can be viewed and >> modified by any user >> 2) Ability for any user to create tickets that can be viewed and >> modified by any list of users, specified for this ticket. >> >> I've taken look at PrivateTickets plugin — it is not what I want. >> >> Is there any plugin that fulfill my needs? >> >> Using trac 0.11. > > > -- And the next thing you know, you're at the zoo, shaving a yak, all so you can wax your car. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
