Inflectra Customer Forums: Incident “Back-Dating” and how best to handle (Thread) We have manual testing sessions using printed sheets and defects from these sessions may not be logged into SpiraTeam until the next day. However, we would like SpiraTeam to show the correct date the incident was identified. What is the best way to handle Back-Dating incidents? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/1783.aspxthreadId=1783Vanessa Smith (vanessa.smith@flhosp.org)Incident “Back-Dating” and how best to handle We have manual testing sessions using printed sheets and defects from these sessions may not be logged into SpiraTeam until the next day. However, we would like SpiraTeam to show the correct date the incident was identified. What is the best way to handle Back-Dating incidents? Tue, 12 Dec 2017 16:37:39 -05002017-12-15T17:23:23-05:00/Support/Forum/spirateam/issues-questions/1783.aspxmessageId=3188Jim R (donotreply5@kronodesk.net) Hi Vanessa, You could add a custom date field to track the dates, or you could load in the inciden Hi Vanessa, You could add a custom date field to track the dates, or you could load in the incidents using the Excel Add-In and specify a backdated Detected Date. Regards Jim Fri, 15 Dec 2017 17:23:23 -05002017-12-15T17:23:23-05:00/Support/Forum/spirateam/issues-questions/1783.aspx#reply3188