[Koha-bugs] [Bug 20885] New: Transferring an item on hold results in bypassing restrictions, actually doing the transfer and can be piled up if repeated

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

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

            Bug ID: 20885
           Summary: Transferring an item on hold results in bypassing
                    restrictions, actually doing the transfer and can be
                    piled up if repeated
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Circulation
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: victor.grousset at biblibre.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com

The first name was «Transferring an item on hold results in chaos»

Disclaimer: I'm not sure if what I did makes sense from a functional point of
view.

== Test plan ==
1. Add transfer restrictions
     staff:/cgi-bin/koha/admin/branch_transfer_limits.pl
     For all item types => clear all
2. Place a hold on a record
3. go to the transfer page staff:/cgi-bin/koha/circ/branchtransfers.pl
4. Try to transfer the item
5. You should see the message «Transfer is not allowed for [...]»
   OR retry with another site to fall into your restrictions
6. But you also see the "Transferred items" table showing the transfer
     This is a bug. The transfer shouldn't have been scheduled.
7. On the same page: redo a transfer
8. You should see "Item is already at destination library."
     This is a bug. This is even worst. The transfer shouldn't have
     been actually done!
9. But wait there is more, the transfer has been add to the table.
     This is a bug. It's still scheduled anyway.
     A transfer to the same branch!
10. Redo it again and it will pile up!
11. Raise your hands and ask loudly: Why!


Tried on master the 24 of April and on version 16.11.15
To ensure that bug 19530 hadn't an influence on this.

Might be related to bug 20344

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