SiT! Bugs - SiT!
View Issue Details
0001344SiT!incidentspublic2010-06-15 14:002010-06-29 16:22
normalminorhave not tried
3.61 LTS 
0001344: Time elapsed per incident
I'm trying SiT for 1 week now to see if it could be used in my enterprise. We are editing a sofware for catering and we have a help desk who need this sort of support. For the moment, he's ok to be integrated but we need one think: we must insert at the closure of the incident the real time needed to resolve the incident. For the moment, SiT make a calcul between the date of opening and the date of closing but this time it's not necesseraly the real time used to resolve the incident.
Could you help me ? It would be great to have a new field in the closure form to indicate the time.

If you need some other informations, do not hesitate.
Thanks for your help. [^]
No tags attached.
has duplicate 0001002assigned Tomse Manual insertion of time spent updating an incident 
related to 0001420assigned Tomse FRP usage per site report 
jpg SiT-Close.jpg (65,294) 2010-06-15 14:00
Issue History
2010-06-15 14:00joceNew Issue
2010-06-15 14:00joceFile Added: SiT-Close.jpg
2010-06-15 14:04ivanRelationship addedhas duplicate 0001002
2010-06-22 17:05TomseStatusnew => assigned
2010-06-22 17:05TomseAssigned To => Tomse
2010-06-22 17:29TomseNote Added: 0003265
2010-06-22 17:45TomseNote Edited: 0003265bug_revision_view_page.php?bugnote_id=3265#r168
2010-06-23 08:46paulhNote Added: 0003266
2010-06-23 11:33TomseNote Added: 0003267
2010-06-29 16:22ivanTarget Version => 4.0
2010-11-22 14:42TomseRelationship addedrelated to 0001420

2010-06-22 17:29   
(edited on: 2010-06-22 17:45)
plugin added to handle this in svn 6515

pluginname : tms_add_timeused

read more here [^]

I've added a thread in the development section to discuss the plugin

2010-06-23 08:46   
This could do to be part of core sit, it also could do to update the service and transactions if billing is enabled
2010-06-23 11:33   
I agree, this is why the reguests are still open, and probably be implemented in 4.2 or 4.3 unless it can be implemented in the earlier 4.x versions.

the plugin is a good workaround solution for the 3.x branch.