Web Client: Random Adjustment to Edit Due Date by One Day

Bug #1800847 reported by Erica Rohlfs on 2018-10-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Evergreen version 3.1

This isn't an easy bug to articulate and is quite random.

Within the patron's items out screen, there is an option to Edit Due Date. For the majority of the time, Evergreen will use the date defined by the user. However, it will randomly adjust the due date by one day. Sometimes this adjustment occurs when the user first logs in. Sometimes is occurs after the user has been using the staff client for a while. Sometimes the adjustment happens on the first try; other times, it randomly adjusts. I've verified that this is not only occurring on dates affected by Daylight Savings, so it's my opinion (for now) that daylight savings is not directly the cause (or the reason for this random occurrence). I will note, however, that the random adjustment rate did occur more frequently around dates affected by daylight savings (such as November 3 and 4).

For example, an item due on Nov 10. I edit the due date to November 3. Evergreen will make the item due November 4. Try again, editing due date to November 3, and Evergreen will then make the item due Nov 3. Same if I edit due date to October 27. Evergreen will randomly mark the item as due October 28. Try again, and it then recognizes Oct 27.

Remington Steed (rjs7) wrote :

Erica, your examples both seem to involve going backwards across the Daylight Savings boundary, which strikes me as a possible cause for the initial bug of setting the date to the following day. I don't know a lot of the details, but it sounds like the difference between setting the due date to "23:59:59" (the end of a day) vs. mistakenly bumping it forward an hour, which becomes "00:59:59" on the next day.


Remington Steed (rjs7) wrote :

This may be the same Daylight Savings Time bug that was just committed at the Hack-a-way:

Bug 1635737: Daylight savings incorrect due dates

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers