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

[Bug 41081] New: Link from 856$u points to http://%20%20%20%20
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41081 Bug ID: 41081 Summary: Link from 856$u points to http://%20%20%20%20 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl http://%20%20%20%20 We should not provide such useless links. The field only contained four spaces. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 43145] New: Add Koha::Health::BackgroundJobs health check
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43145 Bug ID: 43145 Summary: Add Koha::Health::BackgroundJobs health check Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 43137 Target Milestone: --- Follow-up to Bug 43137 (system health monitoring framework). Adds a Koha::Health::BackgroundJobs class that checks: - Workers not picking up jobs (oldest pending job age exceeds threshold) - Failed jobs accumulating without being addressed Alert codes: - jobs_stuck: { code => 'jobs_stuck', params => { count => N, minutes => M } } - jobs_failed: { code => 'jobs_failed', params => { count => N } } Permission: { parameters => 'manage_background_jobs' } The check queries the background_jobs table for: - Jobs with status 'new' where enqueued_on is older than a configurable threshold - Jobs with status 'failed' that have not been acknowledged/cleared Should include full test coverage (mocked, not DB-dependent). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43137 [Bug 43137] Add system health monitoring with status indicators in the staff interface -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 42110] New: Migrate marc_order_accounts.download_directory to use local file transport option
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42110 Bug ID: 42110 Summary: Migrate marc_order_accounts.download_directory to use local file transport option Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org As detailed in bug 41020, we should be using the pre-existing local file transport for marc order accounts. This offers a simple migration path to using FTP/SFTP after migration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 4858] Ability to Charge for Print Notices
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4858 Lisette Scheer <lisette(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Patch doesn't apply CC| |lisette(a)bywatersolutions.co | |m -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 39296] New: Provide a template plugin to return MARC::Record for MARCXML metadata
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39296 Bug ID: 39296 Summary: Provide a template plugin to return MARC::Record for MARCXML metadata Change sponsored?: --- 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org ExtractValue() is a useful MySQL function but it's limited in what it can do. Sometimes, you want to do reporting off a more nuanced understanding of MARC. I had thought about exposing XML::LibXML::Document and XML::LibXML::XPathContext objects, but they're too powerful/vulnerable to abuse. Instead, I decided that MARC::Record should give all the power we need while not upsetting the status quo or security (after all, we already allow access to MARC::Record objects via $biblio objects in Templates). In this case, you fetch the whole "metadata" blob from the database in your report, and you transform it using a template using Koha::Template::Plugin::KohaMarcRecord It lets you perform more advanced reporting using the full MARC record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 43148] New: Batch record deletion for item groups
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43148 Bug ID: 43148 Summary: Batch record deletion for item groups 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: mnero(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Currently batch deletion is only available for bibliographic, authority, and item records. It would be great to be able to delete item groups in a batch as well. Deleting them one by one is very cumbersome because you are redirected to the holdings tab after every single one. If I want to delete a bunch of item groups with no items in them, I have to open a ticket, and it would be easier to do this myself. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 41553] New: Add fund code to fund pulldown for order editor ( neworderempty.pl )
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41553 Bug ID: 41553 Summary: Add fund code to fund pulldown for order editor ( neworderempty.pl ) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It's possible to give multiple funds the same name. It would be helpful to have the fund code in the pulldown options to help disambiguate these funds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 35471] New: Automatically select child MARC framework when adding child records
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35471 Bug ID: 35471 Summary: Automatically select child MARC framework when adding child records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries create their own MARC frameworks for component/child records. When adding a child record through host record, Koha currently selects the default MARC framework and a librarian must manually change to the child record framework. This Bug adds a parent-child relationship to MARC frameworks and aims to skip the manual step of selecting child record framework. The goal is to automatically select child MARC framework when adding child record through the host record. To reproduce problem: Administration -> MARC bibliographic framework 1. Create framework with frameworkcode "A" 2. Create framework with frameworkcode "A-child" Record view 1. Save record with framework "A" 2. Navigate to a record 3. Click "+ New", a drop-down opens 4. Click "New child record" 5. After add biblio form opens, click "Settings" 6. Observe default framework selected 7. You must manually select "A-child framework" After this change, To test: Administration -> MARC bibliographic framework 1. Create framework with frameworkcode "A" 2. Create framework with frameworkcode "A-child" 3. Set "A" as "A-child" 's parent framework Record view 1. Save record with framework "A" 2. Navigate to a record 3. Click "+ New", a drop-down opens 4. Click "New child record" 5. After add biblio form opens, click "Settings" 6. Observe "A-child" framework automatically selected -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 41730] New: Automate change Withdrawn status when item is paid for
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41730 Bug ID: 41730 Summary: Automate change Withdrawn status when item is paid for Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For many libraries, when a lost item is paid for the library does not want the item back -- it should not check in, it should not get marked found, it should not generate a lost fee refund. Functionally, the patron has purchased the book and gets to keep it (should they find it). It would be helpful for Koha to automatically apply a withdrawn status when an item is paid, similar to the UpdateItemLostStatusWhenPaid functionality added in Bug 22740. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 43149] New: Allow option to send mandatory overdue notices if item has a lost status
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43149 Bug ID: 43149 Summary: Allow option to send mandatory overdue notices if item has a lost status Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cmurdock(a)ccfls.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk Target Milestone: --- Currently overdue_notices.pl limits its query for overdue items to those with tems.itemlost = 0 in line 512, so if items have a lost status no notice is sent. In most cases this is probably the desired action, but it would be helpful to have the option to send them for items with a lost status. It could still default to 0 unless otherwise specified in the cron. For example, after all auto renewals have been used, our libraries set overdue items to a lost status of "Long Overdue" after 5 days, while still checked out to the patrons. We have a notice that should be sent at 30 days overdue, but it doesn't get sent because these items have a lost status. Just adding the enhancement request here in case others would find it useful. Cindy -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0