Changes between Initial Version and Version 11 of Ticket #11856
- Timestamp:
- Jul 28, 2015, 1:12:29 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11856 – Description
initial v11 1 The fields //resolution// and //status// in the list of `Ticket.protected_fields` ([browser:/tags/trac-1.0.2/trac/ticket/model.py@:51-52#L49]) are only modified by the workflow. #2045 moves Trac one step closer to adding `owner` to `Ticket.protected_fields` and only allowing the workflow to change the owner field .1 The fields //resolution// and //status// in the list of `Ticket.protected_fields` ([browser:/tags/trac-1.0.2/trac/ticket/model.py@:51-52#L49]) are only modified by the workflow. #2045 moves Trac one step closer to adding `owner` to `Ticket.protected_fields` and only allowing the workflow to change the owner field (see comment:60:ticket:2045). 2 2 3 3 Having `default_resolution` and `default_owner` as attributes of a ticket workflow action and configured through the `[ticket-workflow]` section rather than the `[ticket]` section has a few advantages: … … 6 6 7 7 I've also found the attribute names `set_owner` and `set_resolution` to be a bit confusing. We might consider renaming these to `resolutions` / `owners` or `allowed_resolutions` / `allowed_owners`. 8 9 For completeness, we could also consider adding `restrict_owner` as a workflow attribute, replacing or overriding `[ticket] restrict_owner`. This was mentioned in comment:1:ticket:11976.
