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

[Bug 19133] New: REST API: Password recovery
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '26

22 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19133 Bug ID: 19133 Summary: REST API: Password recovery Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Add password recovery functionality to REST API. Support third party integrations for reset link: by default, use existing password recovery page in Koha OPAC, but also have the ability to link patron to external system to complete their password recovery. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 34629] New: SCO User cannot hold change pickup location branch when OPACAllowUserToChangeBranch is endabled
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '26

22 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34629 Bug ID: 34629 Summary: SCO User cannot hold change pickup location branch when OPACAllowUserToChangeBranch is endabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Turn on the SCO module and enable 'OPACAllowUserToChangeBranch'. 2. Place a hold for a user and then login to the SCO module 3. Under the hold tab try to change the pick up location for an item 4. Notice you are redirected to '/cgi-bin/koha/opac-modrequest.pl' and forced to log in again. 5. Re login to the SCO module and notice the pickup location for thta branch was not updated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41239] New: "cite" feature should display more MARC21 author subfields
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '26

22 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41239 Bug ID: 41239 Summary: "cite" feature should display more MARC21 author subfields Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Currently, the OPAC "cite" feature only displays the MARC21 author 100$a, 110$a, 111$a, 700$a, 710$a and 711$a subfields. However, it is standard MARC21 cataloguing practice to also fill in the 110$b and 710$b subfields - as well as the 111 and 711 $b, $c, $d and $n subfields. The "cite" feature should display the information saved in these other subfields. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 23080] New: Item search: To Call Number Search Not Inclusive
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '26

22 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23080 Bug ID: 23080 Summary: Item search: To Call Number Search Not Inclusive Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)esilibrary.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When conducting an item search and specifying a "To Call Number", the results are not inclusive of the call number specified, contrary to the "(inclusive)" on the form. I have seen this on systems with Library of Congress call numbers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 30144] New: Add support for EDI GIR:LVT, Servicing instructions, segment
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '26

22 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30144 Bug ID: 30144 Summary: Add support for EDI GIR:LVT, Servicing instructions, segment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We allow for free text instructions in the EDI FTX segment now, taken from the vendor notes field. But this is at the order level, it would be helpful to add support for the LVT segment at the line level. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 39757] New: Serial enumeration / chronology sorting is broken again in biblio page
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '26

22 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39757 Bug ID: 39757 Summary: Serial enumeration / chronology sorting is broken again in biblio page Change sponsored?: --- 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In biblio page, subscription sorting is broken again :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 39711] New: Migrate C4::Contract to object classes
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39711 Bug ID: 39711 Summary: Migrate C4::Contract to object classes Change sponsored?: --- 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: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We should migrate this ahead of the new acquisitions work and because it is a relatively small module to migrate -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 40805] New: standardizing labels in the Lists module (private/public label)
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40805 Bug ID: 40805 Summary: standardizing labels in the Lists module (private/public label) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, The Public ou Private criteria hasn't the same name if we create the list from the Lists module or from a catalog search result. it's called 'Public' in the Lists module .Home > Lists > Create new list we have to choose between public and private in the line 'Public:' it's called 'Category' after choosing ‘New list’ from the ‘Add to:’ pull down menu .make a search .select title(s) .click on Add to list .choose ‘New list’ from the pull down menu we have to choose between public and private in the line 'Category:' Couldn't we get the same name for the same thing ? I think Category is right (because reading 'Category: private' seems more logical than 'Public: private') -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 29597] New: Add tomarcplugin option to bulkmarcimport.pl
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29597 Bug ID: 29597 Summary: Add tomarcplugin option to bulkmarcimport.pl 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 This patch provides a tomarcplugin option for bulkmarcimport.pl. There already is a "localcust" option that provides kind of the same functionality, but an option for providing a plugin is for example useful as "to_marc"-plugins can also selected in the "Format" dropdown when staging imports in the staff interface. So if there for example are some marc transformations/processing that should be enforced both routes of import a plugin can be created and used in both cases. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 41265] New: NoIssuesChargeGuarantees and NoIssuesChargeGuarantorsWithGuarantees circulation checks not precise enough
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41265 Bug ID: 41265 Summary: NoIssuesChargeGuarantees and NoIssuesChargeGuarantorsWithGuarantees circulation checks not precise enough 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: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Hello all When a checkout is performed, the NoIssuesChargeGuarantees and NoIssuesChargeGuarantorsWithGuarantees values are checked. This is an ‘if’ statement with check values, but by default, these are empty strings and therefore defined in this way. I therefore believe that the verification is not exactly what we want, particularly when SIP performs the checkout without permission to force it. Furthermore, in kohastructure, the default value would be NULL from what I understand, and it has not been included in the syprefs sql file. Perhaps there are some cases that I am overlooking, but I will suggest a simple fix anyway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7