Quantcast
Channel: Zammad - Community - Latest posts
Viewing all articles
Browse latest Browse all 6761

Timestamp are not correct

$
0
0

Could you do a \d+ tickets and check what datatype your created_at column is in the database? On my Zammad 6.3 test instance, it is timestamp(3) without time zone and I’m curious where your timezone offset in your database is coming from, as it shouldn’t be there.

I reproduced your steps and created a ticket via the webinterface, at around 17:13 (my local timezone, Europe/Amsterdam). It is stored in the database as a UTC timestamp, without the offset:

The Rails console displays the same correct time and timezone for the stored timestamp:
image


Viewing all articles
Browse latest Browse all 6761

Trending Articles