September 2023 - Koha-bugs - lists.koha-community.org

[Bug 30208] New: Marking an item lost should revert the waiting status of any associated hold
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30208 Bug ID: 30208 Summary: Marking an item lost should revert the waiting status of any associated hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If an item is currently Waiting for pickup for a hold, editing that item to apply a lost status should revert the waiting status of the hold. To recreate: - place an item-level hold - check your item in and confirm the hold - confirm on waitingreserves.pl that Koha shows the item is waiting for pickup - confirm on the request.pl that Koha shows the item is waiting for pickup - edit your item to Lost - confirm the item now shows as both lost and waiting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21236] New: Restore ability to selectively set item to lost without generating fee
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21236 Bug ID: 21236 Summary: Restore ability to selectively set item to lost without generating fee Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Prior to bug 19974 a user could set an item to lost via additem.pl and the item would not be marked as returned and the patron would not be charged the replacement cost. The previous bug sought to standardize behavior between additem.pl and moredetail.pl, making both pages mark lost items and returned and charge the patron. Based on feedback about existing library workflows that relied upon the discrepancy between to two behaviors, the MarkLostItemsasReturned syspref was added to give libraries a choice of when and if an item would be marked as returned when set to lost. However, no such syspref was added to give the option to maintain the inconsistent legacy behavior in charging replacement costs when items are lost. This breaks existing workflows for libraries using lost status to handle Claims Returned items where the intent is to mark an item as lost but not charge the patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 32770] New: Patron search field groups no longer exist
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32770 Bug ID: 32770 Summary: Patron search field groups no longer exist Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Prior to bug 30063 we had a number of options in the patron dropdown that were grouped fields. I.e. choosing 'Address' would search accross multiple address fields . These have been lost, with no way for libraries to recreate them. The mappings were: standard => C4::Context->preference('DefaultPatronSearchFields') || 'surname,firstname,othernames,cardnumber,userid', email => 'email,emailpro,B_email', borrowernumber => 'borrowernumber', phone => 'phone,phonepro,B_phone,altcontactphone,mobile', address => 'streetnumber,streettype,address,address2,city,state,zipcode,country', -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 33301] New: Request for adding a facility to remember the previous item location and switch back to it upon check-in.
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33301 Bug ID: 33301 Summary: Request for adding a facility to remember the previous item location and switch back to it upon check-in. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: rajujogi.t(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl For example an item with location code 'GEN' is sent for binding and the current location is now 'SFB' (Sent for binding) and when that item comes back to library from bindery, it's location should automatically be switched back to 'GEN' upon check-in. Since items with different location codes form the list of items being sent for binding, remembering the previous location will help Koha system to automatically set the locations back to the respective original locations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 30901] New: Add template method to be able to look up renewal data in Koha slips and notices
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30901 Bug ID: 30901 Summary: Add template method to be able to look up renewal data in Koha slips and notices Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to be able to report renewals used/remaining in some notices and slips. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 33211] New: Fix failing test for basic_workflow.t when adding item
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33211 Bug ID: 33211 Summary: Fix failing test for basic_workflow.t when adding item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It seems something changed and the selector is no longer findable STRACE: /usr/share/perl5/Try/Tiny.pm:123 in Selenium::Remote::Driver::catch {...} /usr/share/perl5/Selenium/Remote/Driver.pm:361 in Try::Tiny::try (eval 1840):1 in Selenium::Remote::Driver::__ANON__ (eval 1842):2 in Selenium::Remote::Driver::__ANON__ /usr/share/perl5/Selenium/Remote/Driver.pm:1340 in Selenium::Remote::Driver::_execute_command /usr/share/perl5/Selenium/Remote/Driver.pm:1340 in (eval) t/db_dependent/selenium/basic_workflow.t:207 in Selenium::Remote::Driver::find_element Error while executing command: no such element: Unable to locate element: //div[@id="subfield952w"]/input[@class="input_marceditor flatpickr-input"] at /usr/share/perl5/Selenium/Remote/Driver.pm line 411. at /usr/share/perl5/Selenium/Remote/Driver.pm line 356. # Looks like your test exited with 255 just after 6. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 16/22 subtests Test Summary Report ------------------- t/db_dependent/selenium/basic_workflow.t (Wstat: 65280 Tests: 6 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 22 tests but ran 6. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 24319] New: When RenewSerialAddsSuggestion is used, use existing record when ordering from suggestion
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24319 Bug ID: 24319 Summary: When RenewSerialAddsSuggestion is used, use existing record when ordering from suggestion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When renewing a serial subscription a suggestion in the acquisition module can be automatically created using the RenewSerialAddsSuggestion system preference. While the biblionumber can be stored, this will create a new record on 'ordering from a suggestoin' later on. It would be much better, if we attached the order to the existing record instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24318] New: When RenewSerialAddsSuggestion is used, treat suggestion as "order from subscription"
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '23

28 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24318 Bug ID: 24318 Summary: When RenewSerialAddsSuggestion is used, treat suggestion as "order from subscription" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment, you can add add a suggestion on renewing a subscription, using the RenewSerialAddsSuggestion system preference. The suggestion is disconnected from the subscription, as we don't store the subscription id. When the suggestion is accepted, a new record is created and there is no connection to the existing one. We should store the subscriptionid and treat the order as a 'order from subscription', which will give it all the features available for subscription ordering at the moment and form a good connection between the serials and acq modules. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 33477] New: POST /holds/ allows invalid item-level hold if biblio_id and item_id are both specified
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '23

28 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33477 Bug ID: 33477 Summary: POST /holds/ allows invalid item-level hold if biblio_id and item_id are both specified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov CC: tomascohen(a)gmail.com To reproduce: 1. Locate or create a bib with multiple items 2. Set one item to type "Reference" and the rest to type "Book" 3. Go to the Circulation and Fines Rules > "Default holds policy by item type" section, and add a line specifying No Holds Allowed for Reference item type 4. Attempt to place an item-level hold on the Reference-type item via the REST API, specifying only the parameters: patron_id, item_id, and pickup_library_id 5. Confirm expected error message: Hold cannot be placed. Reason: notReservable 6. Attempt to place an item-level hold on the Reference-type item via the REST API, specifying only the parameters: patron_id, item_id, biblio_id, and pickup_library_id 7. Observe that an item-level hold has been placed on the Reference-type item, even though it should not be holdable -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24092] New: Change Koha::Item to use Items::LastPatrons instead of ItemLastBorrower resultset
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '23

28 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24092 Bug ID: 24092 Summary: Change Koha::Item to use Items::LastPatrons instead of ItemLastBorrower resultset Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Koha::Item uses my $items_last_returned_by_rs = Koha::Database->new()->schema()->resultset('ItemsLastBorrower'); to retrieve item's last borrower. It should use Items::LastPatrons class introduced in bug 23260 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4