Evergreen

Expire date remains null when frozen holds are automatically thawed

Bug #1944383 reported by Jessica Woolford on 2021-09-20

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Evergreen	Confirmed	Medium	Unassigned

Bug Description

Evergreen 3.5+

When a hold is suspended, the expiration date is unset to keep it from expiring while it is in this state. If it has an activation date, the expiration date is not restored when the hold the hold thawing script runs.

For consistency, a new expiration interval should be applied at this time, as this is what happens when the hold is thawed manually in the OPAC or staff client.

See IRC conversation: http://irc.evergreen-ils.org/evergreen/2021-09-20#i_491617

Tags:

Jessica Woolford (jwoolford) on 2021-09-20

tags:

added: holds

Jason Stephenson (jstephenson) on 2021-09-20

Changed in evergreen:
status:	New → Confirmed
importance:	Undecided → Medium

Revision history for this message

Jason Stephenson (jstephenson) wrote on 2021-09-20 (last edit on 2021-09-20):

I have confirmed this by looking at the code and counting holds with a null expire_time before and after running the thaw_expired_frozen_holds.srfsh script. It reported thawing 842 holds on my test database, and the number of holds with frozen = 'f' and expire_time is null increased by 842.

Dan Briem (dbriem) on 2021-10-15

tags:

added: circ-holds
removed: holds

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.