D
Daniel Mazzella
When using the API to get the custom date fields of a task they're returned as 04:00 in the
local time of the user making the edit
. This would be fine for us except there is no recording of the users local time, or even which user was the last to update a field.
We have users all around the world and when a user in a time zone with offset greater than UTC+0400 updates a task the "date" part of the date field is shifted back a day.
For example: If a user in Auckland New Zealand selects Nov 5th, 2023 ("2023-11-05") in a date field the API returns Nov 4th, 2023 ("2023-11-04T15:00:00.000Z", after being converted from the Unix timestamp). We have no means of reliably recovering the
actual date
that was selected.
It would be trivial to recover the
actually selected
date if we had the time zone of the user that updated the info.