SiT! Bugs - SiT!
View Issue Details
0000052SiT!incidentspublic2008-07-11 17:342011-07-05 12:28
ivan 
 
normalfeatureN/A
confirmedopen 
 
4.0 
0000052: Edit updates after they are saved
Some users have asked to be able to edit updates after they have been saved
to the incident log. We have deliberately not provided this feature up to
now since the log is supposed to be a historical record.

However it may be useful to allow editing of updates for a short time (say
up to five minutes) to allow edits in the case of typo's or other mistakes
during entry of the update text.
No tags attached.
Issue History
2008-07-11 17:34kieranNew Issue
2008-07-11 17:35kieranNote Added: 0000003
2008-07-14 17:45ivanReporterkieran => ivan
2008-07-14 17:45ivanStatusnew => confirmed
2008-07-14 17:45ivanCategoryother => incidents
2008-07-14 17:45ivanTarget Version => 3.60
2009-08-21 14:29kieranTarget Version3.60 => 4.0
2011-02-14 13:25ivanTarget Version4.0 => 3.90beta1
2011-07-05 12:28ivanNote Added: 0004098
2011-07-05 12:28ivanTarget Version3.90beta1 => 4.0

Notes
(0000003)
kieran   
2008-07-11 17:35   
Date: 2008-01-21 18:55
Sender: paulheaney
Logged In: YES
user_id=1496915
Originator: NO

I can see times when this could be useful.

If this was to be implemented I think the following safeguards should be
implemented

- Enable/Disable feature by admin ($CONFIG ?)
- User only able to update there updates
- The change should be recorded (even displayed in the log) so you can see
what changed (e.g. if you update the incident with "phoned customer asked
to follow document X" then you realise this will cause problems and change
it to "document Y" there would be no record that you had asked the customer
to do X and when they ring up and say your advice caused a problem you have
an accurate and reliable record of what was said)
                            

Date: 2008-01-21 15:48
Sender: nobody
Logged In: NO

This is a feature that I would like - would be useful to go back and tweak
any errors/typos in an update.

I appreciate that the log should be a historical record. How about having
a configurable time limit for changes, and the ability to disable the
feature completely for people who don't want it?
                            

Date: 2008-01-21 15:28
Sender: kieran_hogg
Logged In: YES
user_id=1872958
Originator: NO

Could possibly be done with adapting the existing drafts code?
(0004098)
ivan   
2011-07-05 12:28   
Bumping to v4.0 to help us meet our Roadmap targets for 3.90