ticket restrict-owner list should include TICKET_CHGPROP users

[epearson@…]

I'd like to have the "assign-to" list of users include users that don't necessarily have TICKET_MODIFY permission set — they would need to have the ability to change the ticket, so perhaps requiring TICKET_CHGPROP. This would allow developers to be assigned to work on an issue, mark it (i.e. in a custom field) as "ready for QA", and then have QA be solely responsible for resolving the ticket after retest.

[sid]

Is it really that important that the user not be able to append a new comment to the ticket, yet still own it? TICKET_MODIFY seems perfectly suited, and then you can just implement a "business rule" to tell certain people not to add superfluous comments to the tickets.

Propose a wontfix resolution to this.

[osimons]

Agree with Sid. And with 0.11 this is doable as a plugin on all levels for those that should really want such a feature; ITemplateStreamFilter to modify how things look (like disable commenting), new permission policy api to basically freely set permissions along any dimension, or using the ITicketManipulator interface to veto certain changes being made.