Issue: Ticket Close time is before Create Time

[mustu]

Hi,

I recently did upgraded my application from OTRS 3.0.10 to 3.0.11. I have used the RPM based installer. New app is working fine until I discovered yesterday that the Ticket Create and Close Time are wrong. Below is a sample from some tickets I searched and extracted in CSV. The close time is before the create time. It has ruined all the reports we do generate. Any clue how to fix it?

TicketNumber..............Age........... Created..................Closed
2012011910000580 ….. 2 h 46 m ….. 2012-01-19 13:00:19 ….. 2012-01-19 05:07:11
2012011910000070 ….. 14 h 26 m ….. 2012-01-19 01:20:18 ….. 2012-01-19 05:32:41
2012011910000050 ….. 14 h 46 m ….. 2012-01-19 01:00:19 ….. 2012-01-18 17:11:43
2012011910000040 ….. 14 h 56 m ….. 2012-01-19 00:50:17 ….. 2012-01-18 16:23:53
2012011810001500 ….. 19 h 46 m ….. 2012-01-18 20:00:21 ….. 2012-01-18 11:02:43
2012011810001480 ….. 19 h 56 m ….. 2012-01-18 19:50:18 ….. 2012-01-18 10:28:26
2012011810001230 ….. 21 h 26 m ….. 2012-01-18 18:20:17 ….. 2012-01-18 14:08:21
2012011810001010 ….. 23 h 26 m ….. 2012-01-18 16:20:23 ….. 2012-01-18 15:02:37
2012011810001000 ….. 23 h 26 m ….. 2012-01-18 16:20:21 ….. 2012-01-18 07:40:09
2012011810000870 ….. 23 h 56 m ….. 2012-01-18 15:50:22 ….. 2012-01-18 05:55:42
2012011810000810 ….. 1 d 0 h ....….. 2012-01-18 15:00:34 ….. 2012-01-18 07:47:15
2012011810000660 ….. 1 d 2 h ....….. 2012-01-18 13:00:18 ….. 2012-01-19 02:41:36
2012011810000490 ….. 1 d 4 h....….. 2012-01-18 11:20:21 ….. 2012-01-18 10:08:24

[mustu]

Hi,

I have resolved this issue. It was caused because the timezone of MYSQL was different then the OS. When we do search tickets within OTRS the time on all updates looks fine. But when we do geenrate a CSV of the search results the time in create ticket column comes from OS timezone and the time in remaining close, last update etc columns comes from the MYSQL timezone.