Due date steadily decreases by one each day
Resources
FE @jschatz1
This was brought up by @maxraab at https://gitlab.com/gitlab-org/gitlab-ce/issues/29170#note_25969322
Is there a reason for the steady decreasing due date?!
@godfat I observe this since several days .. yesterday the due date was Mar 12.
It's a bit funny that it's Mar 11 now. I don't think anyone changed the date. I started to think that it's due to timezone issues. We have different people on different timezones updating the descriptions there. It could be possible that even we didn't touch the date, the system thought the time changed due to not considering timezone.
Not sure why it's steadily decreasing by one each day though. Could just be a coincident.
Edit: Adding @mikegreiling's bug report here
Milestone start and end dates change unexpectedly on edit
Summary
Editing and saving a milestone causes the start and end dates to change unexpectedly.
Steps to reproduce
-
Create a milestone with a start and end date provided.
-
Edit the milestone and click save (without altering anything)
-
Notice that the start and end dates are now one day earlier than they were before.
Every time you repeat step 2 this happens.
What is the current bug behavior?
Milestone dates change even when you haven't changed them
What is the expected correct behavior?
Milestone dates should only change when you change them
Relevant logs and/or screenshots
First time clicking edit:
Second time clicking edit:
Output of checks
n/a
Results of GitLab environment info
This bug was reproduced in my local GDK
Possible fixes
This could possibly be due to timezone differences?