Bug 27921: Log correct timestamp for HOLD MODIFY when set waiting
authorJonathan Druart <jonathan.druart@bugs.koha-community.org>
Thu, 11 Mar 2021 15:11:15 +0000 (16:11 +0100)
committerJonathan Druart <jonathan.druart@bugs.koha-community.org>
Thu, 1 Apr 2021 16:51:37 +0000 (18:51 +0200)
commitcb03909af62585aa7a280cd49b2008b0e7b2cbb8
treeeb664e16dd7ab0f4d92a3f585b50ec7f43be4c29
parent6840e8d6fb05dd8c4915f30b925f5a229ded13c3
Bug 27921: Log correct timestamp for HOLD MODIFY when set waiting

The HOLD MODIFY log at the end of ModReserveAffect is not using an
up-to-date $hold object.

$hold is modified at
1201         $hold->set_waiting($desk_id);
But not refreshed before logged (and so the timestamp is not logged
correctly).

Test plan:
Turn on HoldsLog
Place an item on hold
Check it in to mark it waiting

Confirm that the timestamp logged is the one from the check in, not when
you created the hold

Signed-off-by: Owen Leonard <oleonard@myacpl.org>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
C4/Reserves.pm
t/db_dependent/Reserves.t