Changes between Initial Version and Version 4 of Ticket #11873
- Timestamp:
- Apr 30, 2017, 11:08:31 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11873
-
Property
Status
changed from
new
toclosed
-
Property
Resolution
changed from
to
fixed
-
Property
Summary
changed from
more documentation about the lists of availible fields would be helpful
toMore documentation about the lists of available fields would be helpful
-
Property
Status
changed from
-
Ticket #11873 – Description
initial v4 1 I was unable to find a documentation page that lists all of the available values that can be included in ticket notifications. Is there a direct mapping of names in the trac UI to fields? I extrapolated from the existing examples that ${ticket.description}seems to work, but what other fields can be included?1 I was unable to find a documentation page that lists all of the available values that can be included in ticket notifications. Is there a direct mapping of names in the Trac UI to fields? I extrapolated from the existing examples that `${ticket.description}` seems to work, but what other fields can be included? 2 2 3 3 Also, is it possible to use sets in some way? For example, I'd like to be able to send a notification email only if the ticket.component is one of the components (A,B,C)