[Koha-bugs] [Bug 11947] New: Hold priorities not re-calculated when hold is confirmed on checkin.

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

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11947

            Bug ID: 11947
           Summary: Hold priorities not re-calculated when hold is
                    confirmed on checkin.
 Change sponsored?: ---
           Product: Koha
           Version: 3.14
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: bartonski at gmail.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

When checking an item which has multiple holds, clicking 'confirm hold' does
notcause the priorities of the remaining reserves to be re-calculated.

I started testing with the bib record for the book 'After Henry'. There were 3
items under this bib record.

I created six test borrowers:

+-----------+---------+------------+
| firstname | surname | cardnumber |
+-----------+---------+------------+
| bws a     | tester  | bws000     |
| bws b     | tester  | bws001     |
| bws c     | tester  | bws003     |
| bws d     | tester  | bws004     |
| bws e     | tester  | bws005     |
| bws f     | tester  | bws006     |
+-----------+---------+------------+

I checked items out to the first three borrowers:

+---------------+----------------+-----------+---------+------------+
| title         | barcode        | firstname | surname | cardnumber |
+---------------+----------------+-----------+---------+------------+
| After Henry / | 00101000066353 | bws a     | tester  | bws000     |
| After Henry / | ILEA000137401- | bws b     | tester  | bws001     |
| After Henry / | 33080000109101 | bws c     | tester  | bws003     |
+---------------+----------------+-----------+---------+------------+

I checked in the item with barcode '00101000066353' and clicked the 'Confirm
hold' button.

Checking reserves at this point, I saw the following:

+-----------+---------+------------+----------+---------------+
| firstname | surname | cardnumber | priority | title         |
+-----------+---------+------------+----------+---------------+
| bws d     | tester  | bws004     | 0        | After Henry / |
| bws e     | tester  | bws005     | 2        | After Henry / |
| bws f     | tester  | bws006     | 3        | After Henry / |
+-----------+---------+------------+----------+---------------+

Note that the priorities *should* be 0, 1, 2 at this point.

when I check out to 'bws d tester', the priority 0 hold is removed, but the
other two holds are not re-prioritized:

+-----------+---------+------------+----------+---------------+
| firstname | surname | cardnumber | priority | title         |
+-----------+---------+------------+----------+---------------+
| bws e     | tester  | bws005     | 2        | After Henry / |
| bws f     | tester  | bws006     | 3        | After Henry / |
+-----------+---------+------------+----------+---------------+

When holds are displayed and the list does not start with priority 1, the holds
display out of order, with holds showing at the bottom of the list with
priority'1', even though there are no items with priority 1. See the attached
screenshot'Screenshot from 2014-03-14 11-37-13.png', which was taken
immediately after 'bws d tester' was checked in.

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