ticket.status variable not available in email notifications

[pacome.massol@…]

with 0.10 we had a ticket.status available in email notifications. If I try to use this variable with 0.11.1, no email is sent. This variable is really useful to customize notifications.

[Christian Boos]

Right, we used to pass everything to the template:

  self.hdf.set_unescaped('ticket', self.ticket.values)

[anonymous]

Thank you. 0.11.6 is planned in 9 months. Until this version, is there a workaround for 0.11.1 ?

[Christian Boos]

Well, if someone feels like fixing it earlier, we can always move the ticket to an earlier milestone.

In general, tickets scheduled for 0.11.5 are those we really want to fix for the next maintenance release, even if there's no patch provided. OTOH, tickets scheduled for 0.11.6 just mean "for a later maintenance release". So you don't even have a guarantee this will happen in 9 months…

[anonymous]

what would be the equivalent code to pass it to the templates now? or this does not make sense any more?

[Christian Boos]

Hm, sorry, I didn't read the code carefully enough, that ticket variable should actually contain all the values from the real Ticket instance, so it should already work…

But the basic problem remains the same - if you really care about the problem, you should also consider spending some time investigating and debugging the issue yourself and contribute the result back in form of a patch. Otherwise, thanks for the report and someone else may have a look, when time permits (I haven't use notifications myself since a while and don't have the appropriate setup for testing, otherwise yes, I would probably have checked and fixed the problem already).

[anonymous]

Sorry, it's working fine. I was confused by some strange problems with my mail system.