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

[Bug 30668] New: UpdateItemLocationOnCheckin spams the cataloguing log
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30668 Bug ID: 30668 Summary: UpdateItemLocationOnCheckin spams the cataloguing log 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 Cart location updates were moved to this system preference, but for libraries utilizing it this way, the cataloguing log records a change per checkin. We should prevent these changes from being logged -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 18816] New: Make CataloguingLog work in production by preventing circulation from spamming the log
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18816 Bug ID: 18816 Summary: Make CataloguingLog work in production by preventing circulation from spamming the log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The system preference CataloguingLog is not recommended for use in production. This is do to the fact that every checkin and checkout generates one or more log entires. This seems to be not only bad behavior, but unnecessary and outside the needs of CataloguingLog as we have CirculationLog. -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 16544] New: Changes to circ rules should be logged.
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16544 Bug ID: 16544 Summary: Changes to circ rules should be logged. 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At present, changes to circulation rules are not logged. This means that there is no way to determine what circulation rules were in effect at a given time, which makes historical trouble-shooting impossible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 27235] New: Add gzip to package dependencies
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27235 Bug ID: 27235 Summary: Add gzip to package dependencies Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Both koha-dump and koha-translate (since Bug 24211) use gzip. While it appears to be installed in Debian/Ubuntu by the time we run Koha, we should explicitly reference it as a dependency. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 24401] New: REST API: Check-in
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24401 Bug ID: 24401 Summary: REST API: Check-in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 159

[Bug 36165] New: Update "Tools" landing page to be more consistent with 'Cataloging' and 'Circulation' landing pages
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36165 Bug ID: 36165 Summary: Update "Tools" landing page to be more consistent with 'Cataloging' and 'Circulation' landing pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Blocks: 36164 We should take inspiration from existing landing pages, Cataloging, Circulation, Reports, and Administration all come to mind. It would be great to have all of these manifest in a more consistent form. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36164 [Bug 36164] Bring more consistency to our module landing pages -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 35370] New: There should be a system preference to disable checking for holds when issuing an item
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35370 Bug ID: 35370 Summary: There should be a system preference to disable checking for holds when issuing an item 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some library systems want the patron with an item in hand to always be able to checkout the item. It should be possible to configure Koha to ignore holds when issuing items -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 23649] New: Elasticsearch offer an option to weight search results by type
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23649 Bug ID: 23649 Summary: Elasticsearch offer an option to weight search results by type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Some libraries would like to be able to prioritize "books" over "large print" , audios, etc in the search results -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 91

[Bug 24483] New: When batch deleting patrons, report who was not deleted and why
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24483 Bug ID: 24483 Summary: When batch deleting patrons, report who was not deleted and why Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using the batch patron deletion tool, patrons are not deleted if: - They have current checkouts - They have a non-zero balance - They are the guarantor to another patron - They are of a patron category of type staff But Koha never specifically tells the user which borrowers out of their defined pool for deletion are not deleted or why. To test: - Create a patron list - Add to that list one patron for each of these conditions: -- one patron with an item checked out -- one patron with a non-zero balance -- one patron who is a guarantor -- one patron in a staff category -- one patron not meeting any of the conditions above - Go to batch patron deletion, attempt to delete all patrons on your list - Koha tells you 1 patron will be deleted Ideally, Koha would give a list of which patrons will not be deleted and why. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 31572] New: E-mail and SMS verification
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31572 Bug ID: 31572 Summary: E-mail and SMS verification Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I believe Koha has a basic level of e-mail verification with patrons that self register, but it would be helpful if there were a verification method for e-mail and SMS on both staff and patron sides. The idea is, that when an e-mail address or SMS number is entered by staff or patron, there would be a button next to each that would say something like 'Verify'. Staff or patron would click the button, and a link is sent to the e-mail address or number with an explanation (instantly, not through a queue). If the patron clicks the link within a specified amount of time, the button next to that address or number goes away, replaced by the word 'Verified!'. Until the number or address is verified, notices will not go through that method. Notices would only go out through methods that are setup and verified. A step further would be to have another button next to it on the staff side that would be something like 'Re-verification Request'. If staff get bounced e-mails or texts, it would put the address or phone number back to a verification needed mode, and stop all notifications through that method until verified again. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14