[Koha-bugs] [Bug 14937] New: Expiration date for holds based onReservesMaxPickUpDelay should not require ExpireReservesMaxPickUpDelay
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Thu Oct 1 18:58:43 CEST 2015
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14937
Bug ID: 14937
Summary: Expiration date for holds based
onReservesMaxPickUpDelay should not require
ExpireReservesMaxPickUpDelay
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Notices
Assignee: koha-bugs at lists.koha-community.org
Reporter: kyle.m.hall at gmail.com
QA Contact: testopia at bugs.koha-community.org
C4::Letters::_parseletter will replace reserves.expirationdate with the date a
hold will be marked as problematic ( holds over ) if both
ReservesMaxPickUpDelay and ExpireReservesMaxPickUpDelay are enabled. There is
no reason this feature needs to rely on ExpireReservesMaxPickUpDelay as there
are many libraries that would like to send the last day to pick up a hold in
notices, but would rather deal with the expired waiting holds manually rather
than have Koha cancel them automatically.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list