January 2026 - Koha-bugs - lists.koha-community.org

[Bug 40871] New: voided payments still appear as bankable in the register
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40871 Bug ID: 40871 Summary: voided payments still appear as bankable in the register Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk When voiding a payment, the payment still appears as bankable in the register. To recreate: 1. Make sure registers are turned on and you know the current bankable amount. 2. Make a cash payment on a patron account. 3. Observe the bankable amount on that register has increased (as expected). 4. Void this payment on the patron account. 5. Note that the bankable amount has not decreased. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[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 40948] New: Transport cost matrix needs form validation
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40948 Bug ID: 40948 Summary: Transport cost matrix needs form validation Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When testing bug 40655, I noticed that while there is an alert that warns you if you enter an invalid value in a cell "Cost must be expressed as a decimal number >= 0" it only runs onblur, but you can still submit the form with invalid values. If you submit the form with an empty cell, you get an error "There were problems with your submission Invalid value for Centerville -> Fairfield" and the cell does not render an input anymore. It also let's you enter non numeric values which could cause unexpected results. To recreate: 1. Enable UseTransportCostMatrix and go to Administration > Transport cost matrix 2. Click in any cell 3. Uncheck the disabled box (don't click in the cell) 4. Click save 5. Notice the error "There were problems with your submission Invalid value for Centerville -> Fairview" 6. Notice the form is broken for that cell -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[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

[Bug 41336] New: Vue Router warn on Vue datatable pages
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41336 Bug ID: 41336 Summary: Vue Router warn on Vue datatable pages Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Vue pages with a dataTable are giving warns like the following: [Vue Router warn]: No match found for location with path "/cgi-bin/koha/preservation/settings/processings" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 38079] New: Add ability to choose sorting for holdings table
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38079 Bug ID: 38079 Summary: Add ability to choose sorting for holdings table Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 We should add the option for sorting the holdings tables on details display -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 38482] New: Disable save state for items tables
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38482 Bug ID: 38482 Summary: Disable save state for items tables Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com On the holdings table of the bibliographic record detail page, we have a special behaviour: we hide columns if there is no data to display. Indeed we have a lot of column and we want to limit the number of columns displayed. This behaviour conflicts with "Save state": when the columns are hidden the state is modified. If you leave the page and come back, the column will stay hidden, even if the global settings does not have it as hidden and even if the user didn't explicitly hide it. We want to implement something correctly to prevent a conflict with those 2 behaviours, but 24.11.00 is coming and we need a quick fix: here we are going to remove save state for these 2 tables. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 37225] New: Cascade failed notices
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37225 Bug ID: 37225 Summary: Cascade failed notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently in Koha when a notice fails, nothing happens until the library staff rectifies the email or phone number of the patron. Then the library staff can resend the notices from the notices tab. It would be nice if Koha could provide the ability to cascade a failed notification to a secondary notification method. For example, if the sms fails because the mobile number is incorrect, Koha would send an email. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 41586] New: Spacing problem in display of patron names
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41586 Bug ID: 41586 Summary: Spacing problem in display of patron names Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Under some circumstances there are extra or missing spaces around the information displayed by patron-title.inc, particularly the "othername" value. -- You are receiving this mail because: You are watching all bug changes.

1 14