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

[Bug 38441] New: ILL - Allow for a history check workflow stage
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38441 Bug ID: 38441 Summary: ILL - Allow for a history check workflow stage Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com A workflow stage that performs a check on whether an ILL request being placed has already been placed in the past or not. -- You are receiving this mail because: You are watching all bug changes.

1 131

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

06 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 57

[Bug 23336] New: Add an API endpoint for issuing an item to a patron
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 Bug ID: 23336 Summary: Add an API endpoint for issuing an item to a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com The Checkouts API route RFC (https://wiki.koha-community.org/wiki/Checkouts_endpoint_RFC) proposes a POST on /checkouts, which makes sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 110

[Bug 27607] New: Add the ability to compare patron records during merge process
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27607 Bug ID: 27607 Summary: Add the ability to compare patron records during merge process Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We can use the jsdiff library to compare a subset of patron fields during the patron merge process. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 41842] New: Improve translation of course reserves headings
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41842 Bug ID: 41842 Summary: Improve translation of course reserves headings Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Page title, headings, and legends could use some improvements to how they are translated, with more consistent use of context and placeholders -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 35104] New: We should warn when attempting to save badly encoded MARC records
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35104 Bug ID: 35104 Summary: We should warn when attempting to save badly encoded MARC records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 34549 Bug 34549 adds some defensive coding to prevent incorrectly encoded MARC data getting into the database.. but is does so by silently stripping bad characters from the record. It would be nice to highlight that this is taking place, or preferably before it takes place so the end user understands what's happening. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34549 [Bug 34549] The cataloguing editor allows you to input invalid data -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 371

[Bug 40800] New: TransferArrived needlessly triggers alerts in SIP
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40800 Bug ID: 40800 Summary: TransferArrived needlessly triggers alerts in SIP Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org A SIP check-in incorrectly triggers alerts when receiving items in transit at the destination library due to the NotIssued status combined with the TransferArrived message. When an item in transit is checked in at its destination library via SIP clients (sorters, self-service kiosks), the system generates an alert because it finds both: * NotIssued status (item not checked out to a user), therefore a checkin failure * Transfer receipt message Whilst this combination appropriately provides informational messages in the staff client, it's inappropriate for SIP contexts where automated systems don't require transfer receipt notifications and the alert disrupts workflow. The item status transition works correctly (transit → available), but the SIP response incorrectly signals an alert condition, preventing automated systems like sorters from processing transferred items seamlessly. Expected Behaviour SIP check-in of transit items at destination libraries should complete without alerts, allowing automated systems to process transferred items without manual intervention. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 42112] New: Add option for prompting for renewal, always renewing, or never renewing borrower when changing category
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42112 Bug ID: 42112 Summary: Add option for prompting for renewal, always renewing, or never renewing borrower when changing category Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Bug 32581 - Update dateexpiry on categorycode change introduced extra clicks for libraries that change category codes frequently for administrative reasons. There should be an option to not offer the renewal. Ideally the option could be: Always renew/Ask for Renewal/Never renew I'm not sure if it makes more sense to set as a sys pref or as a "when changing to or away from this category" setting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 42217] New: ERM Usage – Harvesting Twice Does Not Overwrite Data
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42217 Bug ID: 42217 Summary: ERM Usage – Harvesting Twice Does Not Overwrite Data Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk If reports are harvested more than once, the usage_count should be overwritten when the data has changed. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 42077] New: Move RabbitMQ from mandatory to optional and make SQL polling the default
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42077 Bug ID: 42077 Summary: Move RabbitMQ from mandatory to optional and make SQL polling the default Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 41506 On bug 41506 we discussed the option of removing RabbitMQ from the codebase. There appears to be consensus that a sensible first step is to update packages to make RabbitMQ optional and SQL polling the default. I believe this would still allow libraries to use RabbitMQ and even move it to a separate server without it installing on the Koha server. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41506 [Bug 41506] Should we remove RabbitMQ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29