April 2024 - Koha-bugs - lists.koha-community.org

[Bug 20547] New: Add default indicators for authorities (counterpart of 9701)
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20547 Bug ID: 20547 Summary: Add default indicators for authorities (counterpart of 9701) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Bug 9701 adds them at the biblio side. We could do the same for authorities. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 30215] New: "Item found" in accountlines untranslatable
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30215 Bug ID: 30215 Summary: "Item found" in accountlines untranslatable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr When a lost item is returned and refunded to the patron, the accountline description contains "Item found" which is untranslatable. To generate this accountline: 0- Make sure BlockReturnOfLostItems is set to Don't Block 0- Make sure WhenLostChargeReplacementFee is set to Charge 0- In Circulation rules, make sure Default lost item fee refund on return policy is set to one of the Refund options 0- Make sure your item has a replacement price (field v of the item) 1- Check out the item to a patron 2- Change the status of the item to lost The patron should be charged the replacement price 3- Check in the item The patron should have a new credit Lost item fee refund In the description of this new credit, it says "Item found <itemnumber>". I couldn't find "Item found" anywhere in the po files. In fact, when I git grep it, it only shows up in C4/Items. (Also, I'm wondering if the itemnumber is really useful here, I think it will confuse library staff as I myself was confused, but this is not the point of this bug) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34756] New: Cancelling a hold does not cancel the related transfer
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34756 Bug ID: 34756 Summary: Cancelling a hold does not cancel the related transfer Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a hold is confirmed and its pickup location is different from the item's location, a transfer is initiated. If the hold is cancelled, the item remains in transfer whereas it is no longer needed at the transfer destination. Is this normal behaviour ? It seems that staff users should at least see a message about the transfer and maybe have the ability to cancel it. Steps to reproduce: 1. Create an item at library A 2. Place a hold on this item with a pickup location at library B 3. Check in the item at library A 4. Confirm the hold. The item should now be in transit to library B 5. Cancel the hold. There is no message about the probably useless transfer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 35797] New: REST API: Add GET route for patronimage
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35797 Bug ID: 35797 Summary: REST API: Add GET route for patronimage Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: shi-yao.wang(a)inLibro.com CC: tomascohen(a)gmail.com Add GET route to get patronimage database table data -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 31897] New: New hook when indexing with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31897 Bug ID: 31897 Summary: New hook when indexing with Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org This patch adds a new hook "before_index_action" with the action "update". This is run on the array reference to the biblio records that are about to be updated in the Elasticsearch index. With this, a plugin can change the record so that it better suits the index without having to change the actual record in the database (something that might be prohibited or discouraged due to centralised cataloging). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 29948] New: Display author information for researches
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29948 Bug ID: 29948 Summary: Display author information for researches Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29897 Display author's information from 371, 372, 373 (email, activity, etc.) in the same area than identifiers (from bug 29897). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29897 [Bug 29897] Display author identifiers for researchers -- You are receiving this mail because: You are watching all bug changes.

1 66

[Bug 36640] New: Upgrade DataTables from 1.13.6 to 2.x
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 Bug ID: 36640 Summary: Upgrade DataTables from 1.13.6 to 2.x 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 34913 DataTables is now in 2.x releases, so we have more upgrading to do. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34913 [Bug 34913] Upgrade DataTables from 1.10.18 to 1.13.6 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 86

[Bug 28599] New: Add ability to void purchase in point of sale
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28599 Bug ID: 28599 Summary: Add ability to void purchase in point of sale Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Depends on: 23354 If one enters a purchase incorrectly in the point of sale module, one can refund the payments on that purchase in order to correct Koha's understanding of the amount of money the library has taken in. However, those refunds don't do anything to correct the record of how many items were sold. That means that accurate reporting on number of items sold needs to be verifying that none of the payments tied to the purchase have been refunded. It'd be better to be able to just void the whole sale, setting the amounts on the original purchase(s) and payments all to zero, zeroing out the note in the purchase (since we're using that for the quantity of the sale), and giving them a VOID status. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23354 [Bug 23354] Add a 'Point of sale' screen to allow anonymous payments -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 36403] New: Add ability to set default sort order for items that display in the Point of Sale system on pay.pl
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36403 Bug ID: 36403 Summary: Add ability to set default sort order for items that display in the Point of Sale system on pay.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: martin.renvoize(a)ptfs-europe.com CC: martin.renvoize(a)ptfs-europe.com On the Point of Sale page at pay.pl the configure button takes you to the table settings for the invoices table. It would be helpful if those settings also allowed staff to set a default sort order by either code or description. Our use case is as follows: Our Library sells items for the Library, the Friends group and the Library Foundation. As a consequence, we have 30 different types of items that can be sold via the POS system. Our codes mirror the fund codes that are used by our Finance office which is necessary for making our daily deposits to the City. We assigned more easily identifiable descriptions for the items so that staff would be able to use the POS system efficiently at a very busy Information Desk. We purposely named the most used items so that they would sort alphabetically at the top of the list. But the default sort order for the table is by code not description. So it would be very helpful to us to be able to set the default sort order in the table settings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30634] New: Allow to define primary and secondary sorting criteria for item table in OPAC
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30634 Bug ID: 30634 Summary: Allow to define primary and secondary sorting criteria for item table in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 30633 It would be great if we could sort by not only one column, but 2 columns in some cases. A good example would be the items table in staff and OPAC. Something like homebranch, itemtype or homebranch, itemcallnumber would be nice, especially for libraries that use different callnumber schemes at different branches. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30633 [Bug 30633] Move OPACHoldingsDefaultSortField to table settings configuration -- You are receiving this mail because: You are watching all bug changes.

1 2