Bug 13202 - Holds with a future date should be skipped over until that date is current
Summary: Holds with a future date should be skipped over until that date is current
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks: 12630
  Show dependency treegraph
 
Reported: 2014-11-05 12:40 UTC by Kyle M Hall
Modified: 2023-06-08 22:26 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2014-11-05 12:40:42 UTC
Bug 12630 would remove the ability to insert a new hold into the middle of the holds list based on the future hold date.

This is good, as the current behavior allows for "cheating" the holds system to get his or her hold pushed higher up the list of holds. 

A better solution would be for the holds system to skip over any holds where the hold date is in the future.

With this behavior, bug 12630 could be pushed, but not allow one future hold in priority 1 to keep any holds after it from being filled.
Comment 1 Nick Clemens 2022-06-10 15:03:04 UTC
This does actually seem to be the case, bug 9761 even allowed for lookahead to capture some of these. Tests added on bug 12630