- Used Zammad version: 3.3
- Used Zammad installation source:deb
- Operating system: Ubuntu 18.04
- Browser + version: any
Why ticket history time zone not match, on my picture the correct time zone here is with the arrow (GMT+8)
But not match to the full details history like on my sample picture with box.
the reason for this is that the timestamps for e.g. “last_owner_update” are the output of the attributes within the history directly. We do not further parse it to display a specific timezoned time.
Not sure if this is really a bug, it’s technically the exact value that lived within the database to that exact time. Might be more of a enhancement, maybe @martini can give some feedback on that if he finds spare time.
Right. In Zammad UI we usually convert server time (UTC) to local user time (browser time offset). But in the ticket history (for value changes) we currently do not this this server time conversation (because currently we only show the values before and after).
It is an enhancement or a minor bug.
If its ok to you Sir @MrGeneration requesting to create request enhancement or a minor bug for this topic.
I think its useful especially for auditing purposes
More POwer Zammad
Keep Safe to All
Please feel free to create a enhancement request.
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.