Opened 8 years ago
Last modified 7 months ago
#12575 new enhancement
Please improve documentation at TracNotification#Customizingthee-mailcontent — at Version 1
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | notification | Version: | |
| Severity: | normal | Keywords: | bitesized, msoutlook documentation |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
From TracNotification#Customizingthee-mailcontent it's not immediately obvious that the template can reference arbitrary ticket fields; in particular, the example given to better support Outlook actually implies that the best way to get at them is to parse them out of ticket_props.
According to comment:7:ticket:9494, the template can just reference e.g. $ticket.product.
I think the documentation should enumerate the variables that are available to the template, and that the Outlook example should be updated to use such direct references (because, as reported in #9494, the example doesn't work when text wrapping occurs in the ticket_props table).
Change History (1)
comment:1 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Please improve documentation at https://trac.edgewall.org/wiki/TracNotification#Customizingthee-mailcontent → Please improve documentation at TracNotification#Customizingthee-mailcontent |
Note:
See TracTickets
for help on using tickets.
Anyone can modify wiki pages including the TracNotification. Please feel free to improve and contribute.