due date fields allow non-sane due dates
Bug #1016102 reported by
Joseph
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Evergreen Version 2.0.3+
On IRC bshum reports ' 3402-01-06 23:59:59-05' was an allowed due date, we may want dojo to check for unreasonable due dates before allowing them.
<bshum> '3402-01-06 23:59:59-05' for a due date. That looks almost like someone might have scanned an item barcode into a due date field? 34020 could be the prefix for items from a lib in our system.
Changed in evergreen: | |
assignee: | nobody → Zavier (zavierbanks) |
status: | Confirmed → In Progress |
tags: | added: needsrepatch |
Changed in evergreen: | |
milestone: | none → 3.5-alpha |
Changed in evergreen: | |
milestone: | 3.5-beta → 3.5.0 |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | 3.5.0 → 3.5.1 |
Changed in evergreen: | |
milestone: | 3.5.1 → 3.5.2 |
Changed in evergreen: | |
milestone: | 3.5.2 → none |
tags: | removed: webstaffclient |
tags: |
added: needswork removed: needsrepatch |
tags: |
added: circ-checkout removed: checkout |
To post a comment you must log in.
Tested and confirmed in master (2506f44).
You can set a specific due date in the year 3402 and perform a checkout (technically valid, I guess) but the actual due date gets displayed as 13/31/69 10:59PM, however, which is strange.