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

[Bug 4858] Ability to Charge for Print Notices
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4858 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas(a)bywatersolutions.com Keywords| |release-notes-needed -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 27364] New: Making previous patron cardnumbers searchable
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27364 Bug ID: 27364 Summary: Making previous patron cardnumbers searchable Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fiona.borthwick(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 18626 introduced the logging of changes to patron cardnumbers which is great, but this still does not link together previous cardnumbers. Imagine this scenario: A library patron loses their library card. They are issued with a replacement. Old and new cardnumbers are recorded in the Modification log. The old card is found (doesn't matter who finds it) and brought to the library. A member of library staff scan the barcode - get no results. This means they are none the wiser as to who this card belonged to. Would it not be a good idea to allow previous cardnumbers to be searchable? Some libraries may record this information somewhere in the patron record, but a search by cardnumber would be extremely helpful. It would be useful if the cardnumber moved into a linked field automatically when a new cardnumber was entered. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas(a)bywatersolutions.com Keywords| |release-notes-needed -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA --- Comment #65 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- I tidied acqui/addorder.pl to make the QA tools happy. I confirmed that all 4 of Pedro's issues from comment 61 have been addressed. Setting back to PQA for the RM. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 --- Comment #64 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- Created attachment 208602 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208602&action=e… Bug 15248: (QA follow-up) Fix duplicate record display in acquisitions and cataloguing -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #203847|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 --- Comment #63 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Thanks for the review. The new follow-up addresses all 4 findings. The unit tests added to t/db_dependent/Search.t were written with the help of an AI assistant (Claude), then reviewed and run by me. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 --- Comment #62 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 208588 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208588&action=e… Bug 15248: (QA follow-up) Fix duplicate check when editing records - When editing a record, only check for duplicates if a matching rule is configured for the framework - 'Forbid creation of duplicate' no longer prevents saving an existing record: a warning is displayed with an option to save - Request one more match when excluding the edited record, so it does not hide an actual duplicate - Fix the description field when editing a non-default framework Test plan: 1. Apply the patches, updatedatabase and restart_all 2. Follow the steps of the 4 findings in the last QA comment => Finding 1: the record is saved without any duplicate warning => Finding 2: the BKS framework description is editable and saving works => Finding 3: editing biblio 155 warns about biblio 252 => Finding 4: editing biblio 252 shows a warning with 'Yes, save record', and the record can be saved 3. With 'Forbid creation of duplicate' enabled, create a new record with ISBN 0964479621 in the BKS framework => Creation is still forbidden 4. prove t/db_dependent/Search.t Co-Authored-By: Claude Opus 5.5 <noreply(a)anthropic.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42667] New: Split the ability to edit other librarian's reports into a separate permission
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42667 Bug ID: 42667 Summary: Split the ability to edit other librarian's reports into a separate permission Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com My work on bug 42108 has lead me to realize that being able to edit anyone's reports creates a loophole that allows anyone who can create reports to bypass 42108 by simply editing someone else's existing report. Aside from that, this seems like a good idea in general. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78