Restrict edit permission for ticket description to ticket owner

[john.williams@…]

THis is similar to #1316.

It would be very helpful if permissions to edit a ticket's description could be restricted to the owner. This allows the administrator(ahem) to be freed up from changing ticket descriptions all the time, while not giving all users in my developer group the TICKET_EDIT_DESCRIPTION permission.

[b7m1@…]

Agreed. Actually, I would like to see this in a more general case. It would be very nice to have a permission setting for actions only available to the owner of the ticket.
Something like: resolve.permissions = TICKET_OWNER which allows only the ticket owner to resolve the ticket.

[anonymous]

​PrivateTicketsPlugin could be extended to work with TICKET_EDIT_DESCRIPTION, surely?

[anonymous]

I've opened ​#3568 on the trac-hacks wiki to handle permissions in workflow

[norman@…]

(sorry forgot to author the last two comments)

[norman@…]

comment:1 has been implemented in ​VirtualTicketPermissionsPlugin. It creates a permission called 'TICKER_IS_OWNER' that is only given when the current user is the owner of the ticket (there are other new permissions for CC and reporter and groups too)

[Christian Boos]

Ok, so comment:1 is implemented by ​TH:VirtualTicketPermissionsPlugin, which is interesting, but this can't be used to implement the original request.

Maybe for this we would need kinds of virtual groups, the same way we have the built-in authenticated:

• @ticket-owner
• @ticket-on-cc
• @ticket-reporter

The existing permissions (e.g. TICKET_EDIT_DESCRIPTION, but also ATTACHMENT_DELETE for #948) could then be assigned to some of these groups.

Those special groups might be dynamically attached to the user by the TicketSystem (or a plugin) implementing a IPermissionGroupProvider, but then the get_permission_groups must know about the resource for which we're currently checking the permission.

[Norman Rasmussen <norman@…>]

That sounds like a fantastic way to implement the functionality. Would that mean that instead of the ​PrivateTicketsPlugin TICKET_VIEW_REPORTER you would just assign TICKET_VIEW to @ticket-reporter (etc for owner, on-cc).

Would you create virtual groups for -in-owners-group, -in-reporter-group -in-cc-group?

[Emmanuel Blot]

It would be nice to have an "author" special user, along with the existing "anonymous" and "authenticated" ones.

[Ryan Ollos <ryano@…>]

Changed ticket summary to better describe request.

[Christian Boos]

See TracDev/Proposals/EvenFinerGrainedPermissions.

[Peter Suter]

See CookBook/PermissionPolicies#GrantapermissiontotheTicketOwner

[Ryan J Ollos]

Replying to john.williams@…:

It would be very helpful if permissions to edit a ticket's description could be restricted to the owner.

Since 1.3.2 (#12719), authenticated user with TICKET_APPEND or TICKET_CHGPROP can modify description of ticket they reported. This allows the reporter to fix/add to the description.

In addition to the useful tip in comment:18, if you wish the owner to modify the description, you can implement a permission policy similar to DefaultTicketPolicy​. In general, I don't think it makes sense to allow the owner to modify the description of a ticket because it depends on having useful restrictions on who set the ticket owner.

[Ryan J Ollos]

Replying to b7m1@…:

Something like: resolve.permissions = TICKET_OWNER which allows only the ticket owner to resolve the ticket.

The TracWorkflow now has a permissions attribute, so you can restrict an action such as resolve.

[Ryan J Ollos]

Replying to Christian Boos:

The existing permissions (e.g. TICKET_EDIT_DESCRIPTION, but also ATTACHMENT_DELETE for #948) could then be assigned to some of these groups.

#12719 also added ability for authenticated user to delete their own attachments.

[Ryan J Ollos]

Closing as wontfix since this can be implemented with a custom permissions policy, and related enhancements to Trac would be covered under TracDev/Proposals/EvenFinerGrainedPermissions.