-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[bug]: Setting Due Date ends up using the previous day #3903
Comments
Hey @lars1273, we're unable to replicate this issue. Could you schedule a call with us? It would be helpful for our team to debug it. You can schedule the call using this link: Schedule Call |
Do you need me to schedule a call or do you think it's server/client TZ differences combined with the use of the JS Date function? |
I’m facing the same issue. I believe this occurs when configuring a different timezone in the Settings. In my case, I’m using GMT-3 (Brazil/East). The datepicker does not appear to take into account the user’s timezone. |
Same issue here |
Same here - On Firefox and Chrome, for every panel that allows a date picker. v0.16 |
Hey, this issue has been resolved in the cloud version and will be addressed in the upcoming release for the self-hosted version. |
Is there an existing issue for this?
Current behavior
On an issue, when i select a due date of March 12th, it sets the due date to March 11th.
I expect it to be March 12th
Steps to reproduce
Environment
Production
Browser
Google Chrome
Version
Cloud
The text was updated successfully, but these errors were encountered: