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

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42427 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42427 [Bug 42427] Circulation Triggers: form dropdowns should expand into view -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42426 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42426 [Bug 42426] Circulation triggers: inform users of one-at-a-time ruleset editing -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41698] New: Add maintenance script to revert found holds for items currently checked out
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41698 Bug ID: 41698 Summary: Add maintenance script to revert found holds for items currently checked out Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz For reasons unknown, it is possible to get into a situation where an item is both checked out to one patron and associated with a found hold for another patron. We should add a script to Koha to fix items in this situation by reverting the found holds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 41844] New: Save button does not work in cataloging when the first important repeatable field is deleted
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41844 Bug ID: 41844 Summary: Save button does not work in cataloging when the first important repeatable field is deleted Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a MARC subfield is marked as Important and Repeatable in the bibliographic framework, it becomes impossible to delete the first occurrence of that field in the cataloging editor. If the first occurrence is deleted, the Save button does not work and the record cannot be saved. To test: 1- Go to Administration -> MARC bibliographic framework and click View default framework 2- Search for tag 653 and click Edit subfields 3- Click on subfield $a 4- Select Important, Repeatable, In 'Managed in' select tab 6 and in 'Visibility' select: OPAC, Staff interface and Editor 5- Save the framework 6- Find or create a record using the default framework. 7- Add a value in 653$a, clone the field and add a value in the second occurrence then save the record. 8- Edit the record again 9- Delete the first 653 field. 10- Click Save ---> It's impossible to save the record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 42265] New: Spelling: FTP is an abbreviation
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42265 Bug ID: 42265 Summary: Spelling: FTP is an abbreviation Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org koha-tmpl/intranet-tmpl/prog/en/modules/admin/edi_accounts.tt: The upload directory specifies the directory on the ftp site to which orders are uploaded. ftp should be FTP. There are probably also some more occurences. These keep coming up in translations because Webpate notices we have translated FTP and wonders if that can be right and asks for extra confirmation. So each time that check is triggered it requires extra clicks. Another good reason to fix :) -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 26461] New: Incorrect handling of hold levels in SIP2 code
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26461 Bug ID: 26461 Summary: Incorrect handling of hold levels in SIP2 code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com This may need to be split into 2 bugs, but problems are related. The SIP2 specification lists two fields for holds requests: AB - item identifier AJ - title identifier 1 - When placing a hold via SIP we always place a title level hold but only use the 'item identifier' to determine the biblio 2 - When cancelling a hold we use the 'item identifier' to identify the item and will only cancel an item level hold We should allow the use of the 'title identifier' for placing holds, and we should place an item level hold if 'item identifier' is passed or title level if 'title identifier' is passed with no item identifier We should do the same for cancelling. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 39665] New: batch_extend_due_dates should allow to extend dates from a list of patrons and a list of items
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39665 Bug ID: 39665 Summary: batch_extend_due_dates should allow to extend dates from a list of patrons and a list of items Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It you want to extend due date for some patrons, or some items (identified by a report for example), you cannot do it currently. It would be a nice improvement. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27286] New: Patron picture-upload.pl allows arbitrary file extension during upload
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27286 Bug ID: 27286 Summary: Patron picture-upload.pl allows arbitrary file extension during upload Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: saiful(a)semanticconsulting.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 114546 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114546&action=e… Double extension or wrong extension in picture file upload The IT team has flagged two issues with the picture upload tool (Patron Images feature): 1. The tool allows upload of files with double extension. 2. The tool allows upload of files with arbitrary file extension. In essence, the tool does not validate the image file restriction that is mentioned in the top of upload input tag which is: "Only PNG, GIF, JPEG, XPM formats are supported." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 20281] New: Allow translating library names for notices/slips
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20281 Bug ID: 20281 Summary: Allow translating library names for notices/slips 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: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr It should be possible to translate the library names, and it should be possible to use those translated names in notices and slips automatically. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 37025] New: Add CLI tool to generate/delete api keys for a given patron on a Koha instance
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37025 Bug ID: 37025 Summary: Add CLI tool to generate/delete api keys for a given patron on a Koha instance Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I bet this will not immediately go through QA. Please don't hesitate to nitpick. :) Just as a disclaimer, I didn't want any flags, just appropriate positional arguments for the two contexts. That's why it might look unconventional. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62