Implement Description field modification permission outside TICKET_ADMIN level

[anonymous]

I've found a very limiting restriction not being able to give Description field modification permission to users without TICKET_ADMIN privileges.

I see two solutions:

• moving Description field modification permission to TICKET_MODIFY level
• creating a new permission level between TICKET_MODIFY e TICKET_ADMIN (TICKET_SUPERVISOR, for example) with Description field modification permission

[Christian Boos]

I would suggest the first case, provided we also give access to the Description change history (see #2945)

[Christian Boos]

Maybe this should become configurable, e.g.

[ticket]
editable_description = false

(= current behavior, could be the default)

[anonymous]

Replying to cboos:

Maybe this should become configurable, e.g.

[ticket]
editable_description = false

(= current behavior, could be the default)

I think a new permission would be more appropriate. TICKET_ADMIN would of course already have the new permission, but this permission could also be given to other users independent of the rest of the TICKET_ permissions.

[sid]

I think a configuration option is not a great solution because this is really a permissions issue.

Adding to an existing permission (TICKET_CHGPROP or TICKET_MODIFY) would be a good solution. Adding another TICKET_ permission would work as well, but there are quite a few TICKET_* permissions already, and adding too many will start to get tedious if you have to assign permissions for editing every field.

[Christian Boos]

Replying to sid:

Adding another TICKET_ permission would work as well, but there are quite a few TICKET_* permissions already, and adding too many will start to get tedious if you have to assign permissions for editing every field.

Ideally, this would be an EDIT permission on the ticket description field. I wonder if we could add the field granularity to the fine-grained permissions…

It would certainly be more convenient to implement as a new TICKET_EDIT permission, though.

[nulleke76@…]

Another idea is to only allow editing of the description field for TICKET_CHGPROP for people that initiated the ticket (until it is accepted by the person that is assigned to it.) after that the assigned person will be able to edit the ticket description.

[Christian Boos]

Replying to nulleke76@gmail.com:

This could probably be done by a PermissionPolicy plugin, after the TICKET_EDIT permission has been added.

[sid]

#5251 is marked as duplicate of this ticket. It requests finer grained control over ticket permissions. Specifically, it asks for a separate permission for changing the ticket resolution.

[trac-ja@…]

Patch againsts source:trunk@6814​

[trac-ja@…]

I wrote a patch as add TICKET_EDIT_DESCRIPTION permission.

[Christian Boos]

Thanks for the patch (and please once again: could you tell us who's behind the trac-ja@ address, so that we can fix the THANKS file?)

[Christian Boos]

(patch was applied in r6833)

[Christian Boos]

See #8548 for a follow-up.