Edgewall Software

Changes between Version 1 and Version 2 of Ticket #2045, comment 51


Ignore:
Timestamp:
Nov 30, 2014, 3:34:22 AM (9 years ago)
Author:
Ryan J Ollos

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2045, comment 51

    v1 v2  
    11With the proposed changes the ticket workflow is solely responsible for changing the //owner// field in the same way that it's responsible for changing the //status// and //resolution// fields. That makes me think that it might make sense to get rid of the `[ticket] default_owner` option (documented at TracTickets#DefaultValuesforDrop-DownFields). Instead we could have:
    22 * `set_owner_to_component_owner` workflow operation which would behave the same as the `< default >` value of `default_owner` (see th:AdvancedTicketWorkflowPlugin#Description).
    3  * `set_owner_to_reporter` and/or `set_owner_to_self` workflow operation (see th:AdvancedTicketWorkflowPlugin#Description).
     3 * `set_owner_to_reporter` workflow operation (see th:AdvancedTicketWorkflowPlugin#Description).
    44 * `default_owner` attribute of the workflow for use with `may_set_owner` (`set_owner` by definition defaults to the ticket reporter).
    55