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

[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 39261] New: Category charge limits are integers in db but decimals in form
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39261 Bug ID: 39261 Summary: Category charge limits are integers in db but decimals in form Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The noissuescharge, noissueschargeguarantees, and noissueschargeguarantorswithguarantees columns for patron categories are INT 10 in the database but presented as currency units with decimals in staff interface. The form inputs are presented on the /koha-tmpl/intranet-tmpl/prog/en/modules/admin/categories.tt template. For instance, if you save a patron category's "noissuescharge" value as "50.50" it is rounded up to "51" in the database. This is unanticipated behavior for administrators. The alternative to making database changes is to remove the $Price on_editing filters from the template, the decimal pattern regex, and make it clear that these are integers representing a currency unit. This is obviously easier but I don't know how important decimal charges are to other libraries (we could do fine without them). The "noissuescharge" syspref is an integer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 24720] New: Remove special characters from beginning of search fields
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24720 Bug ID: 24720 Summary: Remove special characters from beginning of search fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com The ElasticSearch icu_collation_keyword has weird sorting behavior when field values with some special character (", - or [ for example) as they appear on top when sorting a-z. This patch strips initial special characters so behaves more like one would expect (and more like collations usually sort things). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 29326] New: _ALL_ should not override other rules in UpdateItemLocationOnCheckin
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29326 Bug ID: 29326 Summary: _ALL_ should not override other rules in UpdateItemLocationOnCheckin 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com _ALL_ is stated to override all other rules. However, if you use the CART functionality, that is all this preference is good for. You are not allowed special cases. It would be nice if there were specific rules, that it would override _ALL_. This is how we are used to most circ rules working, and this would be more consistent with behavior. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 36616] New: Ability to stop Complex See Reference authority records from being linked to bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36616 Bug ID: 36616 Summary: Ability to stop Complex See Reference authority records from being linked to bibliographic records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We want to prevent cataloguers from being able to select an authority in the bibliographic edit Catalogue authority plugin if the authority record contains a 260 MARC field. The 260 tag in an authority record indicates that it is a Complex See Reference record and contains an instructional note for the cataloguer. https://www.loc.gov/marc/authority/ad260.html These are typically guidance authorities and not meant to be inserted into the bibliographic record. It would be great to enable a feature that prevented these reference headings from being linked to biblios. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 23641] New: Checkout via camera on phone
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '26

20 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23641 Bug ID: 23641 Summary: Checkout via camera on phone Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would love it if someone could figure out a way to do checkout on a device via camera. Maybe an option to type, but that might be questionable. Barcode on camera would be better. It would be great if a patron could grab a book and check it out. Barring any issues with the checkout (fines/overdues/holds, etc), it could be a quick in and out scenario for patrons. Those libraries that have security measures could be instructed to a station to deactivate pending checkouts. -- You are receiving this mail because: You are watching all bug changes.

1 43