Changes between Version 7 and Version 8 of Ticket #11828
- Timestamp:
- Dec 1, 2014, 7:15:36 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11828
- Property Status assigned → closed
- Property Resolution → fixed
-
Ticket #11828 – Description
v7 v8 33 33 The same replacement could be applied to TracTicketsCustomFields field name. 34 34 35 Speaking of which, it's a bit confusing that the attribute `label` is used for TracTicketsCustomFields, whereas `name` is used for TracWorkflow, considering the attribute do the same thing.35 Speaking of which, it's a bit confusing that the attribute `label` is used for TracTicketsCustomFields, whereas `name` is used for TracWorkflow, considering the attributes describe similar behavior. 36 36 37 37 Anyway, those are just small things and not too important. -
Ticket #11828 – Release Notes
v7 v8 1 Added `label` attribute to the TracWorkflow actions and deprecated the `name` attribute. If neither `name` or `label` is specified, the `label` will be created from the action name by replacing underscores with whitespace.1 Added `label` attribute to the TracWorkflow actions and deprecated the `name` attribute. If neither `name` nor `label` is specified, the `label` will be created from the action name by replacing underscores with whitespace. 2 2 3 3 If not specified, the `label` attribute of TracTicketsCustomFields will be created from the custom field name by replacing underscores with whitespace.