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

[Bug 34521] New: Claim Return should be controlled by system preference
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34521 Bug ID: 34521 Summary: Claim Return should be controlled by system preference Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There is no longer a way to remove the claim return tab from a patron account, even if the library does not have a LOST value set for claims return and ClaimReturnedLostValue system preference is NULL. There should be an option for libraries who do not want to use claim returns to turn it off via system preference so the tab no longer shows on the patron account rather than having to hide it with CSS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 35873] New: Count of returned items to CHECKIN message
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35873 Bug ID: 35873 Summary: Count of returned items to CHECKIN message Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: paivi.knuutinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org If patron returns many items at the same time, it is useful to have list but also count of returned items to CHECKIN message. It works with CHECKINSLIP which is for printing the list of checked in items. There you can also have [% old_checkouts.count %] placeholder for amount of checkedin items. If patron wants email of checkedin items, the [% old_checkouts.count %] placeholder doesn't work on CHECKIN notice. Also <<old_issues.count>> doesn't work on CHECKIN notice. Is it possible to show the amount of checkedin items also on email? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34795] New: Options needed to customize serial collection year display in staff interface and OPAC
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34795 Bug ID: 34795 Summary: Options needed to customize serial collection year display in staff interface and OPAC Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 155619 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=155619&action=e… Display of years of a serial collection that needs grouping This is for libraries with large serial collections. It would be helpful to be able to group years together into decades for display. When there are potentially decades worth of a serial collection the display becomes cluttered with each year as a separate button. Even more cumbersome if there are only a few items for each year. If items can be grouped by decade, it simplifies the display and makes it easier to navigate. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 36564] New: Koha staff interface logs out on homepage refresh with 2FA enforced
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36564 Bug ID: 36564 Summary: Koha staff interface logs out on homepage refresh with 2FA enforced Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: chris.rowlands6(a)nhs.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha will log the staff user out if they refresh the homepage and confirm form resubmission after logging in with 2FA enforced. To reproduce: 1) ensure TwoFactorAuthentication is set to "Enforce" 2) log into staff interface including two factor code 3) refresh the homepage and confirm dialogue box for confirm form resubmission This logs you out. However if you navigate to another page and back a refresh functions normally; also if you don't have 2FA enabled a refresh functions normally. I've not submitted a bug before so please let me know if I've submitted this poorly/incorrectly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 34150] New: Personal name (100a) field missing tag editor on acquisition framework
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34150 Bug ID: 34150 Summary: Personal name (100a) field missing tag editor on acquisition framework Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 152833 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=152833&action=e… Missing tag editor button With the RequireChoosingExistingAuthority set to required for cataloging, this requirement is now enforced on the acquisitions framework. However, the authority field is missing the tag editor to allow a look up. To recreate: 1. Set the RequireChoosingExistingAuthority system setting to required. 2. Make sure the acquisitions framework has the 100 Personal name field 2. In Acquisitions, find a vendor and add to a basket from a new empty record. See that the 100 Personal name field is missing the tag editor button. This is new behavior with 22.11. Previously the required look up was not present with this system setting enabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35035] New: Koha hide field values in reference fields based on $w
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35035 Bug ID: 35035 Summary: Koha hide field values in reference fields based on $w Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The Marc 21 Format for Authority Data includes the possibility to not display data in reference fields (4XX and 5XX) based on the third value of subfield w. "/3 - Reference display One-character alphabetic code that enables the generation or suppression of a cross reference from a 4XX or 5XX field. a - Reference not displayed b - Reference not displayed, field 664 used c - Reference not displayed, field 663 used d - Reference not displayed, field 665 used n - Not applicable" The possibility to hide data is important for example for authority records of trans people. The Metadata Best Practices for Trans and Gender Diverse Resources of the Trans Metadata Collective (2022) includes this recommendation in 3.2.4.2 Technical details (MARC & RDA). Catalogers should be able to record former names to assure findability of resources, but it should be also possible to hide them for the public in compliance with cataloging ethics guidelines. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34578] New: Check-in table should have a column to display hold status
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34578 Bug ID: 34578 Summary: Check-in table should have a column to display hold status Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if the checked in table on the check-in screen would include a column displaying holds status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 34506] New: After deleting record from a search result the link 'Go back to the results' has disappeared
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34506 Bug ID: 34506 Summary: After deleting record from a search result the link 'Go back to the results' has disappeared Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com As was implemented in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5428 the link 'Go back to the results' seems to have disappeared to test: 1. make a search in the staff interface eg "perl" 2. chose a record 3. delete it (maybe including items) 4. in 21.05 there was a link 'Go back to the results', which is no present in 21.11.06 thx mark -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 39676] New: koha-reset-passwd fails
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39676 Bug ID: 39676 Summary: koha-reset-passwd fails Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.liddle(a)wycliff.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Hello! I discovered today that using the command koha-reset-passwd fails on Koha 22.11.25 with the following error: env: ‘/bin/admin/set_password.pl’: No such file or directory The command was run as indicated in --help: sudo koha-reset-passwd instancename userid Directly running the underlying script succeeds: sudo koha-shell -c '/usr/share/koha/bin/admin/set_password.pl --userid userid' instancename In this particular case, the userid takes the form of an email address, and I thought perhaps the '@' symbol may have been problematic, but the command also fails for a userid that follows the default pattern of firstname.surname. Am I doing something wrong, or is there a bug in the command? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34664] New: Notes added to fund not visible unless editing that fund
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34664 Bug ID: 34664 Summary: Notes added to fund not visible unless editing that fund Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Notes added to a fund in acquisitions are not currently visible unless the edit option is selected again for that particular fund. Budget_notes don't seem to appear anywhere in the codebase, except on aqbudgets.tt when editing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2