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

[Bug 43828] New: Libraries sorting by code rather than name
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43828 Bug ID: 43828 Summary: Libraries sorting by code rather than name Initiative type: --- Sponsorship --- status: Product: Koha Version: 26.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Target Milestone: --- I notice that 26.05 is sorting the list of libraries in branches.pl by code rather than the library name. This is not the behavior of previous versions, and it should be sorted by the name. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 43827] New: Localuse system preference to turn off count for first check in of an item
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43827 Bug ID: 43827 Summary: Localuse system preference to turn off count for first check in of an item 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: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- Libraries really like the local use function as a way to easily record in library usage without additional steps (as you just check in an item and if not out of loan, records in items.localuse). However, one issue we are having with this function is that when a new book arrives after ordering we check in the item so the item is set as available. This means that local use is currently recording a count for this acquisition checkin. We would love to see the option of a system preference that would allow us to switch off localuse count for an item's first check-in. This would help us to better rely on localuse for stats collection -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 34962] New: Add a system messages feature to Koha to report issues and failures in a more visible way
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34962 Bug ID: 34962 Summary: Add a system messages feature to Koha to report issues and failures in a more visible way Change sponsored?: --- Product: Koha Version: master 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many web projects have a "system messages" area to report cron failures and things like that. These messages are often dismissable. I think it would be great to have a "system messages" table that we could insert things into to make staff aware that something has failed. What I'm imagining is something like wrapping cronjob code in a try/catch and reporting cronjob failures. This would dovetail with action logs. Action logs lot you got searching for issues. This would put the issue right in front of you and would be trigger by actual failures. It could be used to report records with malformed MARC. It could be used to report items that are missing a required field that Koha assumes exists to function, and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 43826] New: Using Additional fields with Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43826 Bug ID: 43826 Summary: Using Additional fields with Template Toolkit Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Target Milestone: --- Either Additional fields needs to display the ID in the table, or Template Toolkit needs to be able to call up the additional field by the table/name. Right now you have to run a report just to get an ID so you can reference it. And by the way, that ID can vary between systems (test and production). So if there is a way to reference it by name or code rather than a random ID, that would be even better. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 30255] New: Allow skipping "list" step for record batch modification/deletion
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30255 Bug ID: 30255 Summary: Allow skipping "list" step for record batch modification/deletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We encountered an issue using the Batch record modification/deletion-tools for a very large number of records. The "list" step where records can be optionally excluded is not relevant in our use-case and takes forever to load. This patch adds an option for skipping this step and directly enqueue the job for all specified records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 31938] New: Add vendor to subscription search result list
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31938 Bug ID: 31938 Summary: Add vendor to subscription search result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: michaela.sieber(a)kit.edu -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

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

15 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 1

[Bug 38259] New: Adjust DT's lengthMenu option
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38259 Bug ID: 38259 Summary: Adjust DT's lengthMenu option 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 36640 https://datatables.net/reference/option/lengthMenu https://cdn.datatables.net/2.0.0/ """ lengthMenu now easier to use, being an array of values, which can either be integers or a label / value object. The old 2D array form is still supported via the legacy integration. """ """ Legacy DataTables 1.x used a 2D array rather than objects to support languages. The first inner array is the page length values and the second inner array is the displayed options. This is still supported in DataTables 2, although now deprecated. """ Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 43382] New: Item, that is attached to item bundle, does not accumulate checkout stats
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43382 Bug ID: 43382 Summary: Item, that is attached to item bundle, does not accumulate checkout stats Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: anni.maki-mantila(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- Currently, an item that is attached to an item bundle does not accumulate its own checkout stats when the item bundle is checked out to a patron. Checkout stats are only recorded for the item bundle itself, not for the individual items attached to it. However, an item attached to an item bundle is in fact being loaned to a patron when the bundle is checked out. Therefore, the attached item should also accumulate checkout stats. Checkout stats are used as the basis when paying compansations to authors. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 41809] New: Waiting holds fulfilled by another copy should be marked for return to stacks
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41809 Bug ID: 41809 Summary: Waiting holds fulfilled by another copy should be marked for return to stacks Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com This may be related to bug 38650 The use case we have run into is: A patron has a hold waiting on the hold shelf. They check out a different copy on the same bib from the stacks and this copy fulfills the hold. The waiting hold does not appear on the holds with cancellations or holds waiting over X days reports. This causes confusion for our branch staff and items sitting on the hold shelf longer than they should be. Ideally these would move to the holds with cancellation requests report, but I'd be interested if others feel differently. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25