-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue due date affected by time zone #11686
Comments
I guess a better fix is to display the date as UTC (instead of local as right now) while continuing to store |
silverwind
added a commit
to silverwind/gitea
that referenced
this issue
May 29, 2020
Previous version did convert to local time zone which was incorrect because the due date is stored as 00:00 utc and it should not be timezone-converted as it may display a different day. Fixes: go-gitea#11686
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Setting a issue due date send a full UTC date
due_date: "2020-05-25T00:00:00.000Z"
to the backend but depending on the user's time zone, the displayed date may not be2020-05-25
. We should probably convert the time to 00:00 in the user's current time zone and then send UTC for that.The text was updated successfully, but these errors were encountered: