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

[Bug 37557] New: Hiding whole fields in MARC bibliographic frameworks
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37557 Bug ID: 37557 Summary: Hiding whole fields in MARC bibliographic frameworks Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliotheca(a)klastervyssibrod.cz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I based a new MARC bibliographic framework on the default one and don´t need most of the fields there, but do not want to delete them, because it´s possible that I´ll want to use them in the future, so I would rather just hide them. But unluckily it´s only possible to hide the subfields one by one and the whole field disappears only after I hid all of the corresponding subfields - which takes very much time to do and is pretty tedious. So what I suggest is to make it possible to hide whole fields in a MARC bibliographic framework with one click (or even to be able to select more of them at once and then hide them all) without having to hide all the subfields one by one first. (By hiding I mean to uncheck all the visibility options by a subfield, or to check the "Flagged" option there.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[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 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 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 30200] New: Add customizable tabs to interlibrary loan requests list
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30200 Bug ID: 30200 Summary: Add customizable tabs to interlibrary loan requests list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi In staff client, all interlibrary loan requests are loaded into a table regardless of their status. Ability to sort them by status under multiple tabs would make librarians life a lot easier. This Bug adds such feature. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 81

[Bug 31630] New: Batch item deletion no longer shows which items were not removed
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '26

15 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31630 Bug ID: 31630 Summary: Batch item deletion no longer shows which items were not removed Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lnilsson(a)lewistonschools.net QA Contact: testopia(a)bugs.koha-community.org The only warning > given is an unclicked box and when deleting long lists it is hard to notice. > The follow up page use to have a notification stating some barcodes were not > deleted, please help. Thanks, LeeAnn Same problem I had with closed Bug 28353 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 37248] New: [Omnibus] Power to the user
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37248 Bug ID: 37248 Summary: [Omnibus] Power to the user 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 This is for the initiative for helping to ensure that users can do as much of the configuration in the interface rather than the command line. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 36063] New: Add Holds to Pull info to intranet-main page
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36063 Bug ID: 36063 Summary: Add Holds to Pull info to intranet-main page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We often use JS to add a display to the intranet-main page when there are holds to pull. It would be nice to just add that into Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 36644] New: Add option for 'Holds per item group' to circulation rules
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36644 Bug ID: 36644 Summary: Add option for 'Holds per item group' to circulation rules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Not sure if this was a staff interface or hold request bug, so took a stab at it. We need a bit more granularity to hold policy on circulation rules for libraries using item group holds. Currently, libraries can only specify 'holds per record' in circulation rules, which is not a one-size-fits-all-holds solution - if they generally only want patrons to have one hold on a record for, say, books, but their manga collection is also a book item type, they have to set Holds per record (count) to a high or unlimited threshold to accommodate group holds. It would be great if circ rules could indicate a limit to holds per item group to give libraries flexibility in using item groups; many libraries probably only want one hold per item group, but they may have a collection where patrons can make multiple requests per group. Circ rules are a logical place to set this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6