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

[Bug 14962] Temp Shelving Location / On Display Module
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 --- Comment #307 from David Nind <david(a)davidnind.com> --- I'd love to test, but there are a lot of patches and comments for this one. Is it possible to get a consolidated test plan for this one? -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 42911] New: Allow primary and secondary default sorting for holdings table in staff interface
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42911 Bug ID: 42911 Summary: Allow primary and secondary default sorting for holdings table in staff interface Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Along with Bug 30634 - Allow to define primary and secondary sorting criteria for item table in OPAC, the ability to sort by primary and secondary criteria would be useful for the holdings table in the staff interface. (30634 mentions the staff interface in its comment, but filing this separately for the Component.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[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 9598] Ability to split up shipping cost between all items and funds on an invoice
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9598 rwallace(a)franklincollege.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rwallace(a)franklincollege.ed | |u --- Comment #4 from rwallace(a)franklincollege.edu --- Would be a great enhancement for Acquisitions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42905] New: Sugerencias
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '26

24 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42905 Bug ID: 42905 Summary: Sugerencias Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: beatrizadriana.lopez(a)upaep.mx QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk Target Milestone: --- Created attachment 200903 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200903&action=e… Captura de pantalla de un registro en KOHA Hola, como tal no es un error, es una idea. Puede ser que dentro de un registro bibliográfico existente en el menú "Nuevo" colocar "Nueva sugerencia de compra". Actualmente existe la opción de sugerencias; sin embargo, algunas veces la sugerencia es sobre un registro existente. Esto ayudará a que dicha sugerencia quede en el registro que le corresponde. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[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