Edgewall Software
Modify

Ticket #7438 (new enhancement)

Opened 19 months ago

Last modified 4 months ago

Restrict edit permission for ticket description to ticket owner

Reported by: john.williams@… Owned by:
Priority: normal Milestone: next-major-0.1X
Component: ticket system Version: 0.11-stable
Severity: normal Keywords: permissions groups
Cc: b7m1@…, norman@…, ryano@…

Description

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.

Attachments

Change History

comment:1 Changed 18 months ago by b7m1@…

  • Cc b7m1@… added
  • Priority changed from low to normal
  • Version set to 0.11-stable

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.

comment:2 Changed 18 months ago by anonymous

 PrivateTicketsPlugin could be extended to work with TICKET_EDIT_DESCRIPTION, surely?

comment:3 Changed 18 months ago by anonymous

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

comment:4 Changed 18 months ago by norman@…

  • Cc norman@… added

(sorry forgot to author the last two comments)

comment:5 Changed 18 months ago by 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)

comment:6 Changed 6 months ago by cboos

  • Keywords permissions groups added
  • Summary changed from ticet description editing permissions to owner to ticket description editing permissions to owner
  • Milestone changed from not applicable to 0.13

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.

comment:7 Changed 6 months ago by 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?

comment:8 Changed 6 months ago by eblot

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

comment:9 Changed 4 months ago by anonymous

  • Summary changed from ticket description editing permissions to owner to Restrict edit permission for ticket description to ticket owner

comment:10 Changed 4 months ago by Ryan Ollos <ryano@…>

  • Cc ryano@… added

Changed ticket summary to better describe request.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will be changed from (none). Next status will be 'new'
The owner will be changed from (none) to anonymous. Next status will be 'assigned'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.