On Thursday, March 9, 2017 at 10:31:18 AM UTC-8, Peter Suter wrote: > > Hi, > > On 09.03.2017 10:16, Mojca Miklavec wrote: > > Hi, > > > > At MacPorts we have a concept of "maintainers". These are people > > without commit access to our repositories and without any elevated > > permissions. These are volunteers who are responsible for maintaining > > individual packages (providing patches etc.), but all their changes > > need to be approved and committed by "senior" members who do some > > quality control first. This is meant to lower the barrier to entry, > > allowing anyone to volunteer to do the work even if they don't have > > sufficient experience yet. > > > > The problem is that these users get tickets assigned to them, but they > > cannot do anything about them other than leaving further comments and > > adding attachments. They cannot change title, edit description, add > > keywords, CC any further developer to ask for help, ... > > > > Another problem is that people who open a new ticket have no way to > > make any further change to the ticket once they click a submit button. > > > > Is there any way to give more permissions to owners of tickets and to > > those who open the ticket? > > > > There are some ancient potentially relevant tickets, but I suspect > > that they were forgotten after so many years: > > > > https://trac.edgewall.org/ticket/7438 > > https://trac.edgewall.org/ticket/10175 > > > > The request came from one of our users: > > https://trac.macports.org/ticket/53755 > > > > Mojca > > > > Can you try this cook book recipe? > > https://trac.edgewall.org/wiki/CookBook/PermissionPolicies#GrantapermissiontotheTicketOwner > > > Peter >
That looks nice, and similar questions come up quite often so thanks for adding the CookBook recipe. I think we can use a variation to satisfy #1453 (1) on trac-hacks.org. The other point for MacPorts to consider is what permissions are necessary to assign (set the owner of) a ticket. As long as something like the default workflow (1) is used where TICKET_MODIFY is required to assign a ticket, and only "senior members" have TICKET_MODIFY, the permission policy should work fine without further configuration. In this context I'm loosely using "assign" to mean a workflow action with a set_owner operation. In more complex scenarios a special permission (3) may be desirable to restrict who can assign a ticket, thereby granting the elevated permissions. (1) https://trac-hacks.org/ticket/1453#comment:10 (2) https://trac.edgewall.org/wiki/TracWorkflow#BasicTicketWorkflowCustomization (3) https://trac.edgewall.org/wiki/ExtraPermissionsProvider -- 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 https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
