renew items screen allows wacky backdating of due dates

Bug #1034058 reported by James Fournie on 2012-08-07
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Medium
Unassigned

Bug Description

Evergreen: 2.2

Under the menu item Circulation -> Renew Items, it is possible to set the due date to ancient times such as the year 0017. This works ok until you try to check the item in.

Michael Peters (mrpeters) wrote :

We've seen this recently too. I guess the fix would be making sure the due date is sometime in the future?

Changed in evergreen:
status: New → Confirmed
milestone: none → 2.4.0-alpha
importance: Undecided → Medium
Ben Shum (bshum) on 2013-03-03
Changed in evergreen:
milestone: 2.4.0-alpha1 → 2.4.0-beta
Ben Shum (bshum) on 2013-03-17
Changed in evergreen:
milestone: 2.4.0-beta → 2.4.0-rc
Ben Shum (bshum) on 2013-04-27
Changed in evergreen:
milestone: 2.4.0-rc → none
Ben Shum (bshum) on 2013-08-22
no longer affects: evergreen/2.2
Chris Sharp (chrissharp123) wrote :

In current master I'm not able to set the year to 0017, and if I set the date to something in the past, I get a red box around the date and time boxes. I'm not able to reproduce this so assuming it got fixed somewhere along the way.

no longer affects: evergreen/2.3
no longer affects: evergreen/2.4
Changed in evergreen:
status: Confirmed → Incomplete
Andrea Neiman (aneiman) wrote :

3.1.5 web client, I can set the date to 0017-08-08 but the checkin will fail (no visual warning, but if audio alerts are turned on you get the 'Error' audio alert). Any/all backdates have a red box at the top to show you that you're in a backdated mode.

I'm leaving this open though & setting back to Confirmed, because I can see the argument for constraining the backdate to something reasonable like within the preceding year (or, say, the preceding two millennia).

Changed in evergreen:
status: Incomplete → Confirmed
tags: added: webstaffc
tags: added: checkin webstaffclient
removed: webstaffc
Andrea Neiman (aneiman) wrote :

Nope, so, let me amend my above comment while actually in the correct interface -- RENEW -- as opposed to checkin, which is what I was looking at in comment #3.

In the web client, 3.1.5, you can absolutely renew an item with a due date in the past (even in the WAY past) with no error, red box, sound, or other indication that you may be doing a foolish thing.

And then you can't check in the item (database update error) until you manually edit the due date to be something sensible.

Still leaving the confirmation up.

tags: removed: checkin
tags: added: circulation
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers