SiT! Bugs - SiT!
View Issue Details
0000411SiT!incidentspublic2009-01-16 14:092011-02-14 13:18
nicdev 
kieran 
normalfeatureN/A
resolvedfixed 
3.41 
3.90beta1Current GIT 
0000411: Ability to send/forward the entire case history to another person internal or external
sometimes we have to refer to others in the company, and we need to forward (directly from the incident window) the entire case history for review, because the R&D engineering team do not have access to our tracking system.

and the same can be said for sending to outside engineers or even the production engineer in the factory.

No tags attached.
duplicate of 0000289closed  Ability to include whole incident log in an email template 
related to 0000624resolved kieran Incident Update Email Template to include the latest update made 
child of 0000010assigned ivan [META] Basic Escalations 
Issue History
2009-01-16 14:09nicdevNew Issue
2009-04-16 20:47ivanRelationship addedrelated to 0000624
2009-05-11 15:56ivanNote Added: 0001040
2009-05-11 15:56ivanStatusnew => confirmed
2009-12-04 09:55paulhRelationship addedduplicate of 0000289
2009-12-04 09:56paulhNote Added: 0002203
2009-12-04 10:13ivanNote Added: 0002204
2010-02-22 13:56ivanRelationship addedchild of 0000010
2010-04-10 21:17kieranNote Added: 0003010
2010-04-10 21:17kieranAssigned To => kieran
2010-04-10 21:17kieranStatusconfirmed => resolved
2010-04-10 21:17kieranResolutionopen => fixed
2010-04-10 21:17kieranFixed in Version => Current GIT
2010-04-10 21:17kieranTarget Version => 4.0
2011-02-14 13:18ivanFixed in VersionCurrent GIT => 3.90beta1
2011-02-14 13:18ivanFixed in Version3.90beta1 => Current GIT
2011-02-14 13:18ivanTarget Version4.0 => 3.90beta1

Notes
(0001040)
ivan   
2009-05-11 15:56   
This will be possible once we add the appropriate template variable. as discussed.
(0002203)
paulh   
2009-12-04 09:56   
Not really sure of the benefit of this, could be useful in external escalations though suspect its better to send only the pertinent details rather than everything as otherwise you could end up sending lots of irrelevent/confusing details
(0002204)
ivan   
2009-12-04 10:13   
It would probably need to be restricted to only the information that is "customer visible". I also see it being potentially confusing but if it's something that somebody needs I'm all for adding it.
(0003010)
kieran   
2010-04-10 21:17   
Added in git commit http://gitorious.org/sit/sit/commit/b75f4e9279b8c8909ce31428980323f28d783cde [^]

Can be used via the {updatetext} trigger variable. By default it will include one update, adding a trigger parameter e.g. 'numupdates = 5' will add 5 and 'numupdates = -1' will add all (use with caution!)