[Koha-bugs] [Bug 35306] Expired holds are not displayed correctly in staff interface
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Fri Nov 10 20:30:15 CET 2023
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35306
--- Comment #4 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to David Nind from comment #3)
> NOTE: I had a go at testing, but Katron had already signed off. Adding my
> notes/questions anyway.
>
> Hi Lucas.
>
> I had a go at testing, but I couldn't figure out from the test plan or
> description how to set a hold to expired.
>
> Do I have to update this in the database?
Yes, you can't create one from the GUI or only by waiting a few days :)
I used something like this:
update reserves set expirationdate = '2022-01-01', patron_expiration_date =
'2022-01-01' where reserve_id = 11;
> When placing the hold, I can't select a date in the date picker before
> today, and I can't manually enter it - it remains blank.
That's the expected behaviour.
> Also, when I applied the patch, there are now four columns that cannot be
> toggled:
> - checkbox
> - priority
> - expiration (newly added after the patch was applied)
> - pickup library
The change on the expiration date column is intentional.
> In addition, (also before the patch is applied as well), I can't sort on
> several columns, such as Priority, Change priority, Expiration date. The
> ones that do seem to work are Patron, Notes, Date, Pickup library, Details.
> Maybe for some, it doesn't make sense for them to be sortable?
That might be something for a separate bug, but it does make some sense. As
expiration date can be a text or an input field, it's probably removed from
sorting for now?
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list