Edgewall Software

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


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

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2045, comment 51

    v2 v3  
    44 * `default_owner` attribute of the workflow for use with `may_set_owner` (`set_owner` by definition defaults to the ticket reporter).
    55
    6 One nice side effect of eliminating `[ticket] default_owner` will be eliminating the `< default >` value, which is awkward due to the whitespace, and it's not obvious that the value should result in the //Component// owner being set: comment:7:ticket:7979, comment:8:ticket:10825.
     6One nice side effect of eliminating `[ticket] default_owner` will be eliminating the `< default >` value, which is awkward due to the whitespace, and it's not obvious that the value should result in the //Component// owner being set: comment:7:ticket:7979, comment:8:ticket:10825. However, even with a `set_owner_to_component_owner` operation we'd still need to allow `< default >` for `default_owner` if we wish to have the drop-down default to the component owner (as opposed to having a workflow action that strictly assigns to the component owner).
     7
     8If `[ticket] default_owner` is moved to the ticket workflow then `[ticket] default_resolution` should be handled similarly.
    79
    810Also, it's slightly simpler to just use `<none>` rather than allowing both `<none>` and `< none >`. Getting rid of `< default >` would allow us to use just `<none>` without any syntax inconsistencies //within a version of Trac//.