set_owner not considering extra permissions

[Ruedi <ruedi.silvestri@…>]

We created a custom Workflow according to ​Workflow documentation and assigned dedicated permissions using the optional ​tracopt.perm.config_perm_provider.ExtraPermissionsProvider which works fine in principle. The issue reported here is the fact that using .set_owner operation does not consider those users having assigned permissions via ​tracopt.perm.config_perm_provider.ExtraPermissionsProvider but only those having MODIFY_TICKET.

OS: CentOS 5.5 Python: 2.4

[Christian Boos]

All the tickets for {20} from last year have probably been seen multiple times by now, yet are still to be triaged…

[Ryan J Ollos]

To summarize, action.permissions specifies permissions that users must have to carry out the action and action.set_owner specifies a list of users that can be set as the ticket owner. The latter overrides the [ticket] restrict_owner setting. Conversely, when [ticket] restrict_owner = true and action.set_owner hasn't been specified, the select contains all users with a valid sessions that posses TICKET_MODIFY. It sounds like you would like to specify the permission that determines which users populate the list. For example, you might like to specify TICKER_OWNER as the permission that determines whether a user can own the ticket, and thus determines which usernames will populate the list.

If my interpretation of your request is correct, it is a duplicate of #3580.