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

[Bug 39722] New: Remove GetSuggestionFromBiblionumber from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39722 Bug ID: 39722 Summary: Remove GetSuggestionFromBiblionumber from C4/Suggestions.pm Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 41258] New: Add a system preference that requires reason for hold cancellation.
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41258 Bug ID: 41258 Summary: Add a system preference that requires reason for hold cancellation. Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: ahoskins(a)nckls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com It would be nice to have a system preference that requires staff to choose a reason for cancelling a hold. This would elimnate the need to always run a report to find out who cancelled the hold and why. When staff choose the option to not leave a reason, we cannot tell what happened unless we run a report and put the object in the mod log. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 40041] New: Update mailmap for 25.11.x
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40041 Bug ID: 40041 Summary: Update mailmap for 25.11.x Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We missed a few mailmap bits in the 25.05.x release -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 31858] New: TT syntax for ACQORDER notices
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31858 Bug ID: 31858 Summary: TT syntax for ACQORDER notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Add TT syntax for ACQORDER notices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 28732] New: Order and claim emails don't work well with repeatable information
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28732 Bug ID: 28732 Summary: Order and claim emails don't work well with repeatable information Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org There is an issue with how the repeatable part of the notice is figured out. This sets some strict limits to how you can write the notice template. It appears that the repeat will happen from first to the last placeholder from an acq table used in the notice. The <order> tags don't appear to be used at all. Test plan: - Create a basket with more than one order line - Set up a notice called ACQORDER for sending order emails (templats below) - Make sure the vendor has an email set and all checkboxes in the contact are checked - Make sure your system can send emails - Click button "send order e-mail" on the basket summary page ------------------------------------------------ ACQORDER TEMPLATE 1: [%- USE Price -%] Dear... <order>Title: <<biblio.title>> Author: <<biblio.author>> Edition: <<biblioitems.editionstatement>> Year: <<biblio.copyrightdate>> ISBN: <<biblioitems.isbn>> Units: <<aqorders.quantity>> Price: [% <<aqorders.listprice>> | $Price %] EUR </order> Thank you! RESULT: Dear and Thank you only appear once. OK. Dear... Title: ... Author: ... Edition: 1. Auflage, Originalausgabe Year: ISBN: 9783839225837 Units: 1 Price: 13.99 EUR Title: ... Author: Edition: Year: 2020 ISBN: Units: 1 Price: 13.00 EUR Thank you! ------------------------------------------------ ACQORDER TEMPLATE 2: Only addition/change is the second line. [%- USE Price -%] <h2>Order: <<aqbasket.basketname>></h2> Dear... <order>Title: <<biblio.title>> Author: <<biblio.author>> Edition: <<biblioitems.editionstatement>> Year: <<biblio.copyrightdate>> ISBN: <<biblioitems.isbn>> Units: <<aqorders.quantity>> Price: [% <<aqorders.listprice>> | $Price %] EUR </order> </hr> Thank you! RESULT: Order:... and Dear... lines are repeated. For information from the basket this doesn't make sense. If you add a field from the branches table, this doesn't appear to cause any additional repeats. Order: 28.4.2021 Dear... Title: ... Author: ... Edition: 1. Auflage, Originalausgabe Year: ISBN: 9783839225837 Units: 1 Price: 13.99 EUR Order: 28.4.2021 Dear... Title: ... Author: Edition: Year: 2020 ISBN: Units: 1 Price: 13.00 EUR Thank you! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 41170] New: HIghlight previously edited item on add items page
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41170 Bug ID: 41170 Summary: HIghlight previously edited item on add items page Initiative type: --- Sponsorship --- status: 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 31323 fixed the highlighting of an item remaining after the item was saved, however, some libraries found this useful for viewing the item after editing to confirm values. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 39967] New: When LoadSearchHistoryToTheFirstLoggedUser is enabled, search history is added at every page load
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39967 Bug ID: 39967 Summary: When LoadSearchHistoryToTheFirstLoggedUser is enabled, search history is added at every page load Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Steps to reproduce: 1. Enable LoadSearchHistoryToTheFirstLoggedUser and EnableOpacSearchHistory 2. Go to OPAC. If logged in, log out. 3. Go to search history and remove all searches if any. 4. Perform a search, make sure it appears in your search history 5. Log in and go to your search history. See that your unauthenticated search history has been added to your account's search history 6. Reload the page multiple times. See that the unauthenticated search history is re-added after each page reload, making your search history grow every time. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 36752] New: Include "charged items" in the SIP2 Patron Info response
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36752 Bug ID: 36752 Summary: Include "charged items" in the SIP2 Patron Info response Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org If you set Y (at the right position) in the 63 summary request, the 64 should contain "charged items", i.e. the items that you have on loan. The code for handle_patron_info just contains a TODO here :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 29923] New: Do not generate overpayment refund from writeoff of fine
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29923 Bug ID: 29923 Summary: Do not generate overpayment refund from writeoff of fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - turn finesmode on 2 - set circ rule a circ rule to charge fines 3 - perform a checkout that follows your circ rule, setting the due date in the past 4 - run the fines cron and confirm that it generates an accruing fine for your patron 5 - write off that fine 6 - edit your circ rule to remove the fine amount and interval 7 - check your item in 8 - see your patron now has a credit in the amount of the writeoff The overpayment credit should only be generated if we've taken payment on the fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 40787] New: Plugins buttons misaligned when search box is enabled
by bugzilla-daemon＠bugs.koha-community.org 28 May '26

28 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40787 Bug ID: 40787 Summary: Plugins buttons misaligned when search box is enabled Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The buttons in the plugins home page ("Upload plugin" and "View plugins by class") become misaligned when you have the git repository search bar. To recreate: 1. Go to Administration > Manage plugins --> Page looks fine, buttons are aligned nicely 2. Add a github/gitlab repository in koha-conf.xml - In ktd shell, open /etc/koha/sites/kohadev/koha-conf.xml - Somewhere under <config> insert the following (or your own) <plugin_repos> <repo> <name>Solutions inLibro</name> <org_name>inLibro</org_name> <service>github</service> </repo> </plugin_repos> - Save the file - restart_all 3. Repeat step 1 (hard refresh page) --> Buttons are misaligned -- You are receiving this mail because: You are watching all bug changes.

1 26