You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating an event, the default time seems to be "now" in UTC. If the user is for example in UTC+1, the time is already in the past.
It's not too bad since you are supposed to change the dates anyway but could we also just leave the date fields empty?
We should also do a review of the whole flow (user time -> utc -> database -> user time) to make sure time zones are being handled correctly, I'm not confident there are no issues there.
The text was updated successfully, but these errors were encountered:
@akirk said:
When creating an event, the default time seems to be "now" in UTC. If the user is for example in UTC+1, the time is already in the past.
It's not too bad since you are supposed to change the dates anyway but could we also just leave the date fields empty?
We should also do a review of the whole flow (user time -> utc -> database -> user time) to make sure time zones are being handled correctly, I'm not confident there are no issues there.
The text was updated successfully, but these errors were encountered: