Sys Created On Date is very wrong

Katie A
Mega Guru

‎09-17-2015 11:42 AM

Hello,

We noticed some very strange results in our Metrics reports. The "Create to Resolve Duration" metric results show several hundred Incidents that have a Duration in thousands of years.


I was able to determine that the cause is the Sys Created On date on those affected Incidents is very wrong.   There are several hundred incidents that have a Start Date from thousands of years ago in the *first century*, such as year 0019 examples 0019-12-10 23:44:29 and 0023-04-10 23:50:56.

The metric is calculating the difference between Created On date and the Updated On date, so that's why those durations are very large.

gr.start = current.sys_created_on;


gr.end = current.sys_updated_on;


gr.duration = gs.dateDiff(gr.start.getDisplayValue(), gr.end.getDisplayValue());



Since the Sys Created On date is generated by the system in the back-end, what could have caused this issue?

The problem seems to have only affected a subset of incidents thus far but has skewed our manager's reporting capabilities.

To summarize, the Sys Created On date on several hundred Incidents is showing dates from thousands of years ago.


SysCreatedOn_IncidentDateissue.png

Preview file
45 KB
0 Helpfuls
  • 2,457 Views
6 REPLIES 6

randrews
Tera Guru
In response to Katie A

‎09-17-2015 01:26 PM

whoever created the ticket.. the opened by would be the person with the bad date format... we have gone so far as to remove all options other than system from the user preference.


0 Helpfuls

Katie A
Mega Guru
In response to randrews

‎09-17-2015 01:49 PM

Ok so I went in and checked a whole bunch of those users but they all have their preferences set to System Date.



I also looked at the User table and sorted by Date Format and there are only a small handful of users who have set an alternate date formatting.



I also went in and impersonated one of those users who have an alternate date format set, I created an incident and the Created On date appears correctly.



So, it doesn't appear as though this is the cause of the issue. Thanks for your help!


0 Helpfuls