[Koha-bugs] [Bug 9322] New: If multiple transfers exist (from circ/branchtransfers.pl), completing one completes them all

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

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

            Bug ID: 9322
           Summary: If multiple transfers exist (from
                    circ/branchtransfers.pl), completing one completes
                    them all
    Classification: Unclassified
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: liz at catalyst.net.nz
                CC: gmcharlt at gmail.com

To replicate: 

* get an item's barcode
* go to circulation -> transfers
* select a branch to transfer to
* put in your barcode
* submit the transfer
* select a different branch to transfer to
* (I don't know why you would do this, but) put your same barcode in again
* submit the transfer
* select a third branch to transfer to
* (again, I don't know why you would do this, but) put your same barcode in
again
* submit the transfer

A query against the database will show 3 transfers: 

select * from branchtransfers;

+------------+---------------------+------------+---------------------+----------+---------------+
| itemnumber | datesent            | frombranch | datearrived         |
tobranch | comments      |
+------------+---------------------+------------+---------------------+----------+---------------+
|        989 | 2012-12-27 14:31:14 | CPL        |                     | FFL    
 | NULL          |
|        989 | 2012-12-27 14:31:20 | FFL        |                     | FRL    
 | NULL          |
|        989 | 2012-12-27 14:34:22 | FRL        |                     | CPL    
 | NULL          |

You can see it's done something kind of smart, by putting the 2nd transfer to
go from the destination of the first transfer. Makes good sense.

What doesn't make such good sense is that when you complete the first transfer,
the following happens:

select * from branchtransfers;

+------------+---------------------+------------+---------------------+----------+---------------+
| itemnumber | datesent            | frombranch | datearrived         |
tobranch | comments      |
+------------+---------------------+------------+---------------------+----------+---------------+
|        989 | 2012-12-27 14:31:14 | CPL        | 2012-12-27 14:34:36 | FFL    
 | NULL          |
|        989 | 2012-12-27 14:31:20 | FFL        | 2012-12-27 14:34:36 | FRL    
 | NULL          |
|        989 | 2012-12-27 14:34:22 | FRL        | 2012-12-27 14:34:36 | CPL    
 | NULL          |
+------------+---------------------+------------+---------------------+----------+---------------+

All three transfers are received when the first one is. The other two don't
trigger. It's like they never existed.

I think this also happens when you have a reserve triggered transit in addition
to a circ/branchtransfers.pl transit. This is the cause of the occasional "Item
on hold for <patron>, item is already waiting" messages when you would normally
be expecting a "Confirm hold for <patron>" message.

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