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

[Bug 13811] Add verbose option borrowers-force-messaging-defaults
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13811 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs(a)lists.koha-commun |nick(a)bywatersolutions.com |ity.org | -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[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

[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 41052] New: marc_ordering_process.pl should take options for specific accounts and/or directories
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41052 Bug ID: 41052 Summary: marc_ordering_process.pl should take options for specific accounts and/or directories 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For debugging it would be helpful to be able to specify to run only for a single account or file/directory -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 1937] Scan barcode with webcam
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '26

20 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1937 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=23641 -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[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

[Bug 42888] New: Use the device's camera to scan barcode on the document
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '26

20 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42888 Bug ID: 42888 Summary: Use the device's camera to scan barcode on the document Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- If the transaction is performed on a device equipped with a camera (smartphone, tablet, etc.), it could be nice if Koha could use the camera to scan the item's barcode. This could make it easier for users to use the module on their own devices and reduce the risk of errors. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1