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

[Bug 35090] New: Additional fields - marcfield of type 'get' doesn't work in serial subscriptions
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35090 Bug ID: 35090 Summary: Additional fields - marcfield of type 'get' doesn't work in serial subscriptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: julian.maurice(a)biblibre.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com Depends on: 10855 To reproduce, k-t-d: 1) Add a new subscription additional field, visit: http://localhost:8081/cgi-bin/koha/admin/additional-fields.pl?tablename=sub… 2) Add a name, set MARC field '942$c' and MARC field mode = 'Get value from MARC record'. Hit 'save'. 3) Add a new subscription serial, visit: http://localhost:8081/cgi-bin/koha/serials/subscription-add.pl 4) Input a biblionumber with data in it, e.g. '112'. Click 'Next' and 'Ok' on the alert box. 5) Notice the MARC field does not contain any data. 6) Fill in all mandatory fields. Hit 'Test prediction'. Hit 'save'. 7) Notice how the subscription screen does not show any MARC field. 8) Notice how nothing is saved in the database: select * from additional_field_values; I think step 5) should display the data since I believe that is the intended behavior. Anyone able to confirm this? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10855 [Bug 10855] Custom fields for subscriptions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29769] New: Claim return status cannot be changed without checking item in
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29769 Bug ID: 29769 Summary: Claim return status cannot be changed without checking item in Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the addition of bug 24279, libraries can no longer change the status of a claim return without checking the item in, which is not a desired behavior. Example: a library sets an item to claims return, looks for the item for three months per policy, item is not found, status needs to be changed from Claim to Lost so the patron is billed for the item. In this scenario, the item should not be checked in to clear the claim status. Marking the claim as resolved does not allow the status to be changed either. Perhaps this could be a setting with Claims Return system preferences as to whether staff are permitted to change the claim/lost status of an item from moredetail.pl? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 38014] New: Migrate from Font Awesome to Bootstrap Icons
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38014 Bug ID: 38014 Summary: Migrate from Font Awesome to Bootstrap Icons Change sponsored?: --- Product: Koha Version: unspecified 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Font Awesome has moved a larger number of their icon options behind their paywall. With V6 we can no longer use the outline/unfilled versions. I propose moving to the bootstrap icon set https://icons.getbootstrap.com, which is fully open source and has a similar icon font to FA. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 31099] New: [DOCS] Export data tool - setup so database and configuration data can be downloaded
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31099 Bug ID: 31099 Summary: [DOCS] Export data tool - setup so database and configuration data can be downloaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Add information to the manual on how to set up Tools > Export data so that the database and configuration backups are enabled and shown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 38763] New: Missing documentation of export database and export configuration options
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38763 Bug ID: 38763 Summary: Missing documentation of export database and export configuration options Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de Depends on: 8268 Maybe I'm missing it, but I don't see information in the manual about exporting the Koha database or configuration. The feature was added by Bug 8268 and may have been missed because it requires editing of koha-conf.xml? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8268 [Bug 8268] Koha should offer way to backup entire db -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31256] New: Circ rules batch modification
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31256 Bug ID: 31256 Summary: Circ rules batch modification Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 Wouldn't it be nice if you could batch modify rules? Like, I have to set a hard due date for schools each year. Instead of modify each rule individually, it would be great if I could specify all libraries, or specific ones, all rules under that or specific ones, and what I would change. There are times when we have to change the fines to everything, or change the holds to many rules, etc. This would make this job so much easier. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 42585] New: Add ability for Koha to analyze reports and warn for potentially dangerous reports
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42585 Bug ID: 42585 Summary: Add ability for Koha to analyze reports and warn for potentially dangerous reports Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com It is quite possible to write reports in Koha that, when run, create huge temp tables that crash a database server or cause runreport.pl to use so much RAM that the kernel oom-kills Koha. It would be nice if we had a tool built in to Koha to help warn librarians about reports with the potential to bring down a Koha server. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 41514] New: The API should fully respect lead and trail periods for bookings
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41514 Bug ID: 41514 Summary: The API should fully respect lead and trail periods for bookings Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 37707 Currently, the lead/trail period handling for bookings is entirely handled in the UI. We should add handling to the API to ensure these settings are adhered to by third-party consumers too. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37707 [Bug 37707] Lead/Trail times should work in combination -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 41608] New: Ability to select multiple values of a facet in the professional interface
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41608 Bug ID: 41608 Summary: Ability to select multiple values of a facet in the professional interface Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In the professional interface, we should be able to select several values from a facet in a single operation (e.g., several libraries, several languages, etc.), so that Koha applies the "OR" operator between each value (e.g., return documents present in library A or library B) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 114

[Bug 42963] New: Add POST endpoint for cash register cashups
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42963 Bug ID: 42963 Summary: Add POST endpoint for cash register cashups Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- This is part of the Point of Sale to Vue migration tracked under bug 42959. GET /api/v1/cash_registers/{cash_register_id}/cashups already exists but there is no way to record a cashup via the API. The staff interface pages pos/register.pl and pos/registers.pl currently call Koha::Cash::Register->add_cashup() directly from Perl, including a bulk cashup action across multiple registers. This patch should add POST /api/v1/cash_registers/{cash_register_id}/cashups to record a single cashup. It should also settle, as part of the design discussion, whether bulk cashup (cashing up several registers at once) is best modelled as repeated client-side calls to this endpoint or as a genuine batch endpoint. Test plan: 1. Perform a cashup via the new endpoint and confirm it matches the result of the existing Koha::Cash::Register->add_cashup() call. 2. Confirm permissions match the existing cash_management cashup requirement. 3. Add unit tests under t/db_dependent/api/v1/. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1