The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Worklog startdate is saved to worklog table with a different timezone
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?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.