Modify ↓
#11873 closed defect (fixed)
More documentation about the lists of available fields would be helpful
Reported by: | Owned by: | ejucovy | |
---|---|---|---|
Priority: | normal | Component: | WorkflowNotificationPlugin |
Severity: | normal | Keywords: | documentation |
Cc: | Trac Release: |
Description (last modified by )
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?
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)
Attachments (0)
Change History (4)
comment:2 Changed 7 years ago by
Summary: | more documentation about the lists of availible fields would be helpful → More documentation about the lists of available fields would be helpful |
---|
comment:3 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
See wiki:TracDev/DataModels#Ticket. Documented in WorkflowNotificationPlugin@23.
comment:4 Changed 7 years ago by
Description: | modified (diff) |
---|
new_ticket.condition = ${ticket.component in ('A', 'B', 'C')}
would probably also work.
Note: See
TracTickets for help on using
tickets.
I was able to solve the second part of my question using multiple condition lines
new_ticket.condition = ${ticket.component == 'A'} new_ticket.condition = ${ticket.component == 'B'} new_ticket.condition = ${ticket.component == 'C'}
It appears that the behavior is evaluate each of them and send the message if any yields true.