0000010: [META] Basic Escalations

Issue History
Date Modified	Username	Field	Change
2008-07-11 15:39	kieran	New Issue
2008-07-11 15:39	kieran	Status	new => assigned
2008-07-11 15:39	kieran	Assigned To	=> ivan
2008-07-30 19:50	ivan	Relationship added	child of 0000139
2008-10-04 19:25	paulh	Target Version	3.40 => 3.45
2008-11-29 23:32	kieran	Target Version	3.45 => 3.50
2009-05-29 14:58	ivan	Target Version	3.50 => 3.60
2009-07-26 19:52	paulh	Relationship added	parent of 0000811
2009-08-21 14:29	kieran	Target Version	3.60 => 4.0
2010-02-20 17:49	paulh	Note Added: 0002408
2010-02-20 17:49	paulh	Summary	Neat Escalations => Basic Escalations
2010-02-22 13:56	ivan	Relationship added	parent of 0000411
2010-02-22 13:57	ivan	Relationship deleted	child of 0000139
2010-02-22 13:57	ivan	Relationship added	parent of 0000139
2010-02-22 13:57	ivan	Relationship added	parent of 0000960
2010-02-22 13:59	ivan	Summary	Basic Escalations => [META] Basic Escalations
2010-04-10 22:57	ivan	Relationship added	parent of 0000049
2010-04-18 12:09	ivan	Relationship added	parent of 0001284
2011-03-07 10:54	luca	Note Added: 0003667

Notes
(0002408) paulh (administrator) 2010-02-20 17:49	For 4.0 internal escalations is the aim, 4.1 for external

(0003667) luca (reporter) 2011-03-07 10:54	Not sure if a note is the ideal way to do this, i hope it is... Some things which might be useful in creating an escalation: - on selecting an escalation path some of the incident update fields could be auto-completed. (external email address and name at least) giving the chance to immediately create and send the email to the external engineer. - now to escalate you need to edit the incident, would be nice having it as an update option, this way the ticket could be escalated and the status set to something like awaiting external action. Thanks. Luca