Skip to content
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

Closed
1 task done
lars1273 opened this issue Mar 7, 2024 · 8 comments · Fixed by #3992
Closed
1 task done

[bug]: Setting Due Date ends up using the previous day #3903

lars1273 opened this issue Mar 7, 2024 · 8 comments · Fixed by #3992
Assignees
Labels
🐛bug Something isn't working

Comments

@lars1273
Copy link

lars1273 commented Mar 7, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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

  1. Go to an issue
  2. Set the due date
  3. The resulting due date will be the previous day

Environment

Production

Browser

Google Chrome

Version

Cloud

@lars1273 lars1273 added the 🐛bug Something isn't working label Mar 7, 2024
@srinivaspendem
Copy link
Collaborator

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

@psi-chuffine
Copy link

There are several instances of this issue. #3074 #3305 #2204 #1992

It's most likely stemming from server/client TZ differences combined with use of the JS Date function.

@lars1273
Copy link
Author

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?

@leonam-okajima
Copy link

leonam-okajima commented Mar 13, 2024

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.

@apatterson2600
Copy link

Same issue here

@jake-ef
Copy link

jake-ef commented Mar 18, 2024

Same here - On Firefox and Chrome, for every panel that allows a date picker. v0.16

@yepayepayepa
Copy link

I've been facing the same issue in the Cloud and self-hosted versions. I recorded a small video to show you, I agree that it might be a TZ issue
plane

@srinivaspendem srinivaspendem linked a pull request Mar 25, 2024 that will close this issue
@srinivaspendem
Copy link
Collaborator

Hey, this issue has been resolved in the cloud version and will be addressed in the upcoming release for the self-hosted version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants