Edgewall Software

Changes between Version 1 and Version 2 of Ticket #11976, comment 1


Ignore:
Timestamp:
Mar 9, 2015, 7:36:31 AM (9 years ago)
Author:
Ryan J Ollos

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11976, comment 1

    v1 v2  
    1919The `set_owner` and `permissions` attributes have significantly different functions. `reassign.set_owner = TICKET_APPEND` populates the //assign to// list with users having the `TICKET_APPEND` permission. `reassign.permissions = TICKET_APPEND` restricts the //reassign// action to users having the `TICKET_APPEND` permission.
    2020
    21 The `set_owner` attribute is not new, however it's functionality has been expanded. The attribute is documented in [wiki:1.1/TracWorkflow#BasicTicketWorkflowCustomization]. In #11856 I proposed renaming the attribute to `owners`.
     21The `set_owner` attribute is not new, however it's functionality has been expanded. The attribute is documented in [wiki:1.1/TracWorkflow#BasicTicketWorkflowCustomization]. In #11856 I have proposed renaming the attribute to `owners`.
    2222
    2323> (in that some environments may have very large user groups and would prefer the group/permission restrictions without the visible list) and could be done with no compatibility issues for 1.2.x.
    2424
    25 I've considered adding `restrict_owner` to the `[ticket-workflow]` section, making it an action attribute that takes precedence over the `[ticket] restrict_owner` setting. We could then restrict the allowed users using the `set_owner` / `owners` field without having a drop-down list. We could leave the ticket open for handling that feature request.
     25I've considered adding `restrict_owner` to the `[ticket-workflow]` section, making it an action attribute that takes precedence over the `[ticket] restrict_owner` setting. We could then restrict the allowed users using the `set_owner` / `owners` field without having a drop-down list. We could leave this ticket open for handling that feature request.