On Thursday, November 20, 2014 3:13:35 PM UTC-5, RjOllos wrote: > > > On Nov 20, 2014 12:11 PM, "Ryan Ollos" <[email protected] <javascript:>> > wrote: > > > > > > On Nov 20, 2014 11:57 AM, "Shawn Baker" <[email protected] > <javascript:>> wrote: > > > > > > I suppose it is possible that the Agilo plugin (which we are no longer > using) had permissions to not allow anyone but TICKET_ADMIN or the owner of > the ticket to change the status of the tickets. I really thought that Trac > would have something like this out of the box. It seems odd to me that > anyone who is authenticated in the system can change the status of any > ticket as they see fit. > > > > Right, with the default data that ships with trac authenticated users will > have TICKET_MODIFY and therefore be able to change tickets in the default > workflow . The aim is to impose as little on the user as possible, and let > users customize it for their needs. Usually it is simple to customize, but > it does get more complex with specialized requirements such as permissions > depending on ticket properties. If we receive repeated requests for certain > requirements we might try to bundle the functionality into tracopt or > sample-plugins. > > I'll probably add this permissions policy to the CookbBook pages in the > meantime. >
Do I just put the restrict_actions.py file in my plugins directory? I don't need to do anything else with it? -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
