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

[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 42681] New: (Bug 34971 follow-up) serials/serials-collection.pl generates error 500
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42681 Bug ID: 42681 Summary: (Bug 34971 follow-up) serials/serials-collection.pl generates error 500 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: baptiste.wojtkowski(a)biblibre.com Depends on: 34971 When working with subscription without superlibrarian permissions the page /cgi-bin/koha/serials/serials-collection.pl?subscriptionid=NNN generates error 500 with an entry: Can't use string ("NNN") as a HASH ref while "strict refs" in use at /usr/share/koha/lib/C4/Serials.pm line 2792. in plack-error.log. This is because can_edit_subscription called in serials/serials-collection.pl (line ~234) requires a hash reference containing data from the subscription table (or an unblessed Koha::Subscription object), and not subscriptionid. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34971 [Bug 34971] Closing a subscription should require edit_subscription permission -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[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

[Bug 41249] New: ILL batches should be compatible with AutoILLBackendPriority
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41249 Bug ID: 41249 Summary: ILL batches should be compatible with AutoILLBackendPriority Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com AutoILLBackendPriority suggests the top most available backend in priority when creating a new ILL request. This should also work the same when creating requests through the ILL batches functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 37666] New: Make additional fields available via Template Toolkit in notices
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37666 Bug ID: 37666 Summary: Make additional fields available via Template Toolkit in notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It seems that is not possible today (or in a complex way?) to display in notices information stored in additional fields defined in admin/additional-fields.pl It could be nice to add this feature, in the same spirit as https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 42558] New: reserves.reservedate should be datetime instead of date
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42558 Bug ID: 42558 Summary: reserves.reservedate should be datetime instead of date Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In front of work I intend to do on Bug 42524. In order to calculate priorities based on reservedate, the reservedate must include time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 97