You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When we try to add a worklog for `2023-11-16` with a start time of `09:00`, the `startdate` value in the `worklog` table would be `2023-11-16 10:00:00.000 +0200`. As our current time zone is GMT+2 and start time is `09:00`, then should this `startdate` field be 2023-11-16 09:00:00.000 +0200` ?
We also tried to add worklog by changing time zone in user profile and also from different time zones (via Chrome Developer Tools), it does not make any sense and there is still this one hour difference. On the other hand, the other time fields e.g. created and updated displays the time correctly based on the displayed time zone.
So, is there any bug related to saving `startdate` field of `worklog` table? If not, why the start time as for an office having time zone GMT+2 is saved in that field is different than it should be?