[Koha-bugs] [Bug 29594] New: Koha should print transfer slip when generated a transfer from cancelling a hold on Holds Awaiting Pickup

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Nov 29 19:40:14 CET 2021


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

            Bug ID: 29594
           Summary: Koha should print transfer slip when generated a
                    transfer from cancelling a hold on Holds Awaiting
                    Pickup
 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: andrew at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com
        Depends on: 23092

When one cancels a hold with the Cancel button on Holds Awaiting Pickup
(waitingreserves.pl), a transfer may be generated but Koha doesn't prompt you
to print a transfer slip.

Following the changes in bug 23092, this transfer is generated with both a
daterequested and a datesent -- in other words the transfer is immediately
considered Sent.

Since the transfer is already Sent, checking the item in to generate a new hold
slip will generate a "wrong transfer" error message, cancel the first transfer,
and generate a new transfer (which does get a slip).

I see two options to resolve this:

1: We could generate the transfer as Requested rather than Sent. One would then
check the item in to trigger the transfer and get a slip at that point.

2: We could print the transfer slip right away when cancelling the hold.

Answer 1 seems simpler and more in line with the directions transfers are going
in.


Referenced Bugs:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23092
[Bug 23092] Add 'daterequested' to the transfers table
-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list