Bug 33992: Only consider the date when auto-expiring problematic recalls
authorAleisha Amohia <aleishaamohia@hotmail.com>
Tue, 13 Jun 2023 05:29:22 +0000 (17:29 +1200)
committerTomas Cohen Arazi <tomascohen@theke.io>
Wed, 19 Jul 2023 15:06:50 +0000 (12:06 -0300)
commit0d2052088ec62654f81154be0b9916b8e8630891
tree8ac7357652950d92dcd69451245ca06e0d9c3193
parent45b050871e7ed882b553f211db97204f30634646
Bug 33992: Only consider the date when auto-expiring problematic recalls

This patch carries this fix into the misc/cronjobs/recalls/expire_recalls.pl cronjob so that recalls are automatically expired when they have been waiting a problematic number of days, not considering hours, as expected.

To test, follow the test plan from the first patch. This will set you up with a waiting problematic recall.

Run the cronjob manually

perl misc/cronjobs/recalls/expire_recalls.pl

Refresh your 'Recalls awaiting pickup' page. Your problematic recall should be gone/expired.

Expiration dates will apply when expiring any 'unfulfilled' recall i.e. newly requested, overdue to be returned, and awaiting pickup.

Sponsored-by: Auckland University of Technology
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
misc/cronjobs/recalls/expire_recalls.pl