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

[Bug 37434] New: Lists are incorrectly sorted in UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37434 Bug ID: 37434 Summary: Lists are incorrectly sorted in UNIMARC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In UNIMARC, when creating a list using sort by copyrightdate, it sorts using the MARC21 field "copyrightdate", which is not existing in UNIMARC. Note: the inventory search uses the field publicationyear to sort, which is the correct field to use here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 39302] New: Checkin disappear from checkin list if transfer modal is triggered
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39302 Bug ID: 39302 Summary: Checkin disappear from checkin list if transfer modal is triggered Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There is a flaw in the logic of the checkin code: we keep 20 (default value for numReturnedItemsToShow) checkins in the table, but there can be shift in the "counter" logic when the transfer modal is triggered. There are actually several other problems in the logic of this controller but we are going to try and focus on only this one. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 37222] New: Standardize markup for sidebar menus
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37222 Bug ID: 37222 Summary: Standardize markup for sidebar menus Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org We've got a couple of different ways we're marking up sidebar menus, and we're limiting ourselves by tying the style to an ID. There are a few cases where we want to include more than one menu in the sidebar and we shouldn't have to update CSS just to make them consistent. I'm proposing: <div id="circ-menu" class="sidebar_menu"> <ul> ... </ul> </div> -- You are receiving this mail because: You are watching all bug changes.

1 64

[Bug 30961] New: Table Settings Reports table_reports Group and Subgroup does not work
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30961 Bug ID: 30961 Summary: Table Settings Reports table_reports Group and Subgroup does not work Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration 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 In Admin - Table Settings - Reports - table_reports, the Group and Subgroup checkboxes do not hide the respective column in the saved reports page. The Group and Subgroup columns can be hidden from the saved reports page by using the Column Config option there, but they need to be able to be hidden from the Table Settings function. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 32776] New: Choose to convert oldest reserve or all possible reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32776 Bug ID: 32776 Summary: Choose to convert oldest reserve or all possible reserves to recalls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 31415 introduces a script to convert reserves to recalls. By default, it will take the oldest reserve on a record and convert it to a recall. We should be able to customise which reserve(s) are converted to recalls. Options may include: - oldest reserve - one reserve for each issued item available to be recalled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 31415] New: Script to automate converting reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31415 Bug ID: 31415 Summary: Script to automate converting reserves to recalls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record reaches X number of reserves, the library may convert reserves to recalls to prompt patrons to return them sooner. This can be automated with a script. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 35665] New: Should secondary email address be allowed to be used as a CC in notices?
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35665 Bug ID: 35665 Summary: Should secondary email address be allowed to be used as a CC in notices? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I would say yes to this. Maybe have a checkbox next to the secondary email field to cc notices to this address. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 36712] New: Alert "Maximum checkouts calculated from the circulation rule" is wrong with child itemtypes
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36712 Bug ID: 36712 Summary: Alert "Maximum checkouts calculated from the circulation rule" is wrong with child itemtypes Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When trying to checkout an item with a child itemtype, it fails to say that the parent rule applied and says "All item types" Test plan: 1. have an itype BK (Books in sample data) 2. create an itype BK2, set BK as the parent to BK2 3. create a circ rule for All Patrons, item type BK (displays as "Books (All)" in the circ rules interface), setting total checkouts to 1 4. do not create any rule specifically for the BK2 itype 5. have 2 BK2 items (can be on the same bib record) 6. Try to checkout the 2 items 7. The alert mention matched circ rule is for "Item type: All item types" 8. This is wrong -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 35704] New: Parent and child itemtype hold limits not enforced as expected
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35704 Bug ID: 35704 Summary: Parent and child itemtype hold limits not enforced as expected 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Similar to bug 30324, the hold limits aren't enforced for parent/child item types. A parent limit doesn't seem to matter at all in this case. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 35320] New: Deleting a patron doesn't use AnonymusPatron to anonymize the circulation history
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35320 Bug ID: 35320 Summary: Deleting a patron doesn't use AnonymusPatron to anonymize the circulation history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org I was under the impression that when AnonymousPatron is filled with a borrowernumber, deleting a patron (individually or with batch deletion tool) would anonymize their circulation history using AnonymousPatron, but it doesn't. After deleting a or some patrons, the circulation history in the book record shows blank spaces in lieu of the patrons. It would make more sens that when deleting a patron using the batch deletion tool or the delete button in a patron's page, the AnonymousPatron is used to fill the circulation history of the deleted patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5