[Koha-bugs] [Bug 35307] New: Expired holds are missing an input, so updating holds causes loss of data

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35307

            Bug ID: 35307
           Summary: Expired holds are missing an input, so updating holds
                    causes loss of data
 Change sponsored?: ---
           Product: Koha
           Version: 23.05
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: nick at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

In 23.05 when viewing a list of holds expired holds show as 'Expired:
mm/dd/yyyy'

The table is a form, and when submitted, these expired rows have no input - so
the array of expiration dates fetched is out of sync and rows after an expired
hold can have dates set incorrectly.

To test:
1 - Place 3 holds on a bib, each for a different patron
2 - IN the db, set the first hold to be expired:
    UPDATE reserves SET expirationdate='2023-01-01' WHERE reserve_id=1;
3 - Refresh the holds page for the biblio
4 - Note the first hold now says 'Expired' in the expiration date column
5 - Set an expiration date for the last hold
6 - Click 'Update holds'
7 - Note the date is applied to the second hold

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.