SiT! Bugs - SiT!
View Issue Details
0000568SiT!triggerspublic2009-03-11 17:432011-02-14 13:18
nicdev 
kieran 
normalfeatureN/A
resolvedduplicate 
3.45 
3.90beta1Current GIT 
0000568: Add trigger when an incident changes status
Would be nice to have a trigger that fires when an incident changes status back to "active"
No tags attached.
duplicate of 0001261confirmed  Missing templates and triggers for 4.0 
child of 0001089confirmed  [META] triggers revamp 
Issue History
2009-03-11 17:43nicdevNew Issue
2009-03-11 17:49ivanStatusnew => confirmed
2009-03-11 17:49ivanTarget Version => 3.50
2009-03-11 19:09kieranNote Added: 0000775
2009-03-12 11:08ivanNote Added: 0000776
2009-05-30 14:51ivanTarget Version3.50 => 3.60
2009-06-13 09:57kieranNote Added: 0001197
2009-06-13 09:57kieranAssigned To => kieran
2009-06-13 09:57kieranStatusconfirmed => assigned
2009-08-17 12:30kieranTarget Version3.60 => 3.80
2010-02-20 17:05paulhTarget Version3.60 LTS => 4.0
2010-02-20 17:05paulhRelationship addedchild of 0001089
2010-04-12 12:26kieranRelationship addedduplicate of 0001261
2010-04-12 12:26kieranStatusassigned => resolved
2010-04-12 12:26kieranResolutionopen => duplicate
2010-04-12 13:10ivanNote Added: 0003033
2011-02-14 13:18ivanFixed in Version => 3.90beta1
2011-02-14 13:18ivanFixed in Version3.90beta1 => Current GIT
2011-02-14 13:18ivanTarget Version4.0 => 3.90beta1

Notes
(0000775)
kieran   
2009-03-11 19:09   
The way to do this would be to have a trigger on status change and use the rule to specify to fire when the new status is active.
(0000776)
ivan   
2009-03-12 11:08   
This might not be as easy as it sounds to implement because knowing whether the status has changed means knowing the current status, something that we don't always know at the time of writing new status.

That, coupled with the fact that there are a lot of places where status could change makes it a little more work than you'd think. e.g. Update incident, send email, incoming email, portal etc.

Definately one we should look into adding though, I can see it could be very useful.
(0001197)
kieran   
2009-06-13 09:57   
I guess the best way to do this is to have a function to change incident status, we get away from having the same code all over the place plus for instances like this it makes it easy to add code.
(0003033)
ivan   
2010-04-12 13:10   
That would mean the function would need to read the current status and then write the new status. That seems quite expensive?