[Koha-bugs] [Bug 22691] New: Problem with holds when ExpireReservesMaxPickUpDelay is active

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Apr 11 22:07:29 CEST 2019


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

            Bug ID: 22691
           Summary: Problem with holds when ExpireReservesMaxPickUpDelay
                    is active
 Change sponsored?: ---
           Product: Koha
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: patrick.robitaille at collecto.ca
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com
  Target Milestone: ---

Hi, 

It seems that there is a problem affecting reservations set aside. The
ExpireReservesMaxPickUpDelay preference, when it is active, does not seem to
take into account the delay in the ReservesMaxPickUpDelay system preference
which determines the time period for which reservations will be available for
pickup by the users who made the reservation. However, the reservation is to be
canceled during the night the item gets the status « is waiting here ».

To test:
Enable the ExpireReservesMaxPickUpDelay system preference to « Allow»;
Enter a number in the ReservesMaxPickUpDelay system preference to more than 2
days;
Reserve a item for a user;
Return this item to get the hold found message and confirm this reservation;
Wait until the next day and note that the reservation is cleared from the
user's account and the record as well;

So the limit of days specified in the ReservesMaxPickUpDelay system preference
is not taken into account as indicated.

Can it be the cron job that makes this cancellation? Or it turns out that it is
the relationship between the two preferences that is not done correctly?

Thanks, Patrick.

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


More information about the Koha-bugs mailing list