Wrong ticket status ids in automation (CLOSED is 5 not 3 it seems)
Description
For intended operation I had to change the following in vaccumd-configuration.xml
For trigger "selectClosedTicketStateForProblemAlarms"
WHERE a.tticketstate = 3 --> WHERE a.tticketstate = 5
For action "deletePastClearedAlarms"
AND (alarmacktime IS NULL AND (tticketState IS NULL OR tticketState = 3)) --> [..]tticketState = 5[..]
it even says in comment that "<!-- ticket state of 3 is closed -->" --apparently not The same problem is in some others like "deleteAllPastClearedAlarms" (ok, maybe that's the only one)
It caused me quite an headache so I want to spare others the same, thanks
Ben created a branch with the patch applied and I added the beginnings of a more stable solution to be revisited whenever JPA gets bumped to 2.1+.
LibreMan April 30, 2011 at 10:44 AM
Also, I tested RT 4.0 released yesterday or so and it works with the current REST API implementation. I have not run into any problems so far at least ...
For intended operation I had to change the following in vaccumd-configuration.xml
For trigger "selectClosedTicketStateForProblemAlarms"
WHERE a.tticketstate = 3 --> WHERE a.tticketstate = 5
For action "deletePastClearedAlarms"
AND (alarmacktime IS NULL AND (tticketState IS NULL OR tticketState = 3)) --> [..]tticketState = 5[..]
it even says in comment that "<!-- ticket state of 3 is closed -->" --apparently not
The same problem is in some others like "deleteAllPastClearedAlarms" (ok, maybe that's the only one)
It caused me quite an headache so I want to spare others the same, thanks