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

[Bug 43120] New: KohaTable/PatronSearch_spec.ts is failing (randomly?)
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43120 Bug ID: 43120 Summary: KohaTable/PatronSearch_spec.ts is failing (randomly?) Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Koha_Main/3854 08:19:00 <testsuite name="Filters" timestamp="2026-07-21T06:18:17" tests="1" time="0.000" failures="1"> 08:19:00 <testcase name="Filters Keep filters in the column filters" time="0.000" classname="Keep filters in the column filters"> 08:19:00 <failure message="Timed out retrying after 10000ms: Expected to find content: 'Showing 1 to 20 of 42 entries' within the element: <div.dt-info> but never did." type="AssertionError"><![CDATA[AssertionError: Timed out retrying after 10000ms: Expected to find content: 'Showing 1 to 20 of 42 entries' within the element: <div.dt-info> but never did. 08:19:00 at Context.eval (webpack://koha/./t/cypress/integration/KohaTable/PatronSearch_spec.ts:158:52) 08:19:00 at getRet (http://koha:8081/__cypress/runner/cypress_runner.js:120454:20) 08:19:00 at tryCatcher (http://koha:8081/__cypress/runner/cypress_runner.js:1777:23) 08:19:00 at Promise.attempt.Promise.try (http://koha:8081/__cypress/runner/cypress_runner.js:4285:29) 08:19:00 at Context.thenFn (http://koha:8081/__cypress/runner/cypress_runner.js:120465:66) 08:19:00 at Context.then (http://koha:8081/__cypress/runner/cypress_runner.js:120716:21) 08:19:00 at wrapped (http://koha:8081/__cypress/runner/cypress_runner.js:148798:19)></failure> 08:19:00 </testcase> 08:19:00 </testsuite> Same related failure on KohaTable_spec.ts 08:18:04 <testsuite name="Patrons search" timestamp="2026-07-21T06:16:06" tests="3" time="28.389" failures="2"> 08:18:04 <testcase name="kohaTable (using REST API) Patrons search Input search bar and clear filter " time="0.000" classname="Input search bar and clear filter "> 08:18:04 <failure message="Timed out retrying after 10000ms: Expected to find content: 'Showing 1 to 20 of 42 entries' within the element: <div.dt-info> but never did." type="AssertionError"><![CDATA[AssertionError: Timed out retrying after 10000ms: Expected to find content: 'Showing 1 to 20 of 42 entries' within the element: <div.dt-info> but never did. 08:18:04 at Context.eval (webpack://koha/./t/cypress/integration/KohaTable/KohaTable_spec.ts:605:56) 08:18:04 at getRet (http://koha:8081/__cypress/runner/cypress_runner.js:120454:20) 08:18:04 at tryCatcher (http://koha:8081/__cypress/runner/cypress_runner.js:1777:23) 08:18:04 at Promise.attempt.Promise.try (http://koha:8081/__cypress/runner/cypress_runner.js:4285:29) 08:18:04 at Context.thenFn (http://koha:8081/__cypress/runner/cypress_runner.js:120465:66) 08:18:04 at Context.then (http://koha:8081/__cypress/runner/cypress_runner.js:120716:21) 08:18:04 at wrapped (http://koha:8081/__cypress/runner/cypress_runner.js:148798:19)></failure> 08:18:04 </testcase> 08:18:04 <testcase name="kohaTable (using REST API) Patrons search Browse by last name" time="2.649" classname="Browse by last name"> 08:18:04 </testcase> 08:18:04 <testcase name="kohaTable (using REST API) Patrons search Prevent XSS when using description" time="0.000" classname="Prevent XSS when using description"> 08:18:04 <failure message="Timed out retrying after 10000ms: Expected to find content: 'Showing 1 to 20 of 42 entries' within the element: <div.dt-info> but never did." type="AssertionError"><![CDATA[AssertionError: Timed out retrying after 10000ms: Expected to find content: 'Showing 1 to 20 of 42 entries' within the element: <div.dt-info> but never did. 08:18:04 at Context.eval (webpack://koha/./t/cypress/integration/KohaTable/KohaTable_spec.ts:709:56) 08:18:04 at getRet (http://koha:8081/__cypress/runner/cypress_runner.js:120454:20) 08:18:04 at tryCatcher (http://koha:8081/__cypress/runner/cypress_runner.js:1777:23) 08:18:04 at Promise.attempt.Promise.try (http://koha:8081/__cypress/runner/cypress_runner.js:4285:29) 08:18:04 at Context.thenFn (http://koha:8081/__cypress/runner/cypress_runner.js:120465:66) 08:18:04 at Context.then (http://koha:8081/__cypress/runner/cypress_runner.js:120716:21) 08:18:04 at wrapped ( Note that we have just upgraded Cypress (bug 42772) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 42751] New: Circulation log viewer no longer displays item barcode in Info column
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42751 Bug ID: 42751 Summary: Circulation log viewer no longer displays item barcode in Info column Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com After Bug 29016 converted the log viewer to use the AJAX DataTable interface, circulation log entries no longer display the item barcode in the Info column. For CIRCULATION ISSUE and RETURN actions, the previous log viewer displayed a useful item identifier (typically the barcode, often as a hyperlink). The current implementation displays only the itemnumber or a JSON structure containing the itemnumber. Example action log entry: { "branchcode" : "CPL", "confirmations" : [], "forced" : [], "issue" : 1, "itemnumber" : 77 } This is rendered in the Info column as: 77 (linked to moredetail.pl using the itemnumber) The associated item record contains barcode: 39999000001396 Displaying the itemnumber is not particularly useful to staff, who generally identify items by barcode. To reproduce: 1. Enable IssueLog. 2. Check out an item with a known barcode. 3. Go to Tools → Log viewer. 4. Filter by Module = Circulation. 5. Locate the checkout log entry. Current result: * The Info column displays the itemnumber (or raw JSON containing the itemnumber). Expected result: * The Info column should display the item barcode, as it did prior to the AJAX log viewer conversion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 15986] New: Add a script for sending hold waiting reminder notices
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15986 Bug ID: 15986 Summary: Add a script for sending hold waiting reminder notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Write a script that will take two parameters: a) Length of time hold has been waiting ( in days ) b) Letter code of notice to be emailed 2) Script will take these two parameters and send the specified notice for each hold a patron has. -- You are receiving this mail because: You are watching all bug changes.

1 121

[Bug 38509] New: Displayed transfer destination is incorrect when a reservation has been found
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38509 Bug ID: 38509 Summary: Displayed transfer destination is incorrect when a reservation has been found Change sponsored?: --- 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com TEST PLAN FOR 24.05 (transfers appear to be broken on main atm, code is still invalid on main) 1 - Place a hold for Henry Acevedo on "39999000001334" (item level), ask for a pickup at centerville 2 - At centerville, transfer the document to fairfield. There will be a pop-up giving you three choices. The first one is "transfer to centerville", which is not the behaviour or the button. The correct text is "transfer to fairfield". The button must display the branch selected for the transfer and not the pickup location for the reservation (which is the branch at which we are located.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 24843] New: Allow batch change of framework
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24843 Bug ID: 24843 Summary: Allow batch change of framework 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Koha should give users some method to change the framework of multiple records at once. Batch record modification cannot currently do this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 42153] New: Holds override is not reflected in action logs
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42153 Bug ID: 42153 Summary: Holds override is not reflected in action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 40866 To reproduce: 1. Enable HoldsLog and AllowHoldPolicyOverride system preferences 2. Place multiple holds for the same patron on the same biblio record, until Koha shows the "Too many holds for this record" warning (with default KTD/sandbox settings, it will show this warning on the 3rd hold) 3. Click Place Hold 4. View the action logs entry for that hold creation i. Go to Tools > Log viewer ii. Select Modules: Holds and Action: Create iii. Click Submit --> The "info" column should show a "HOLD_POLICY_OVERRIDE" confirmation, but it doesn't! Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40866 [Bug 40866] Corrections to override logging -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 43118] New: library_id in List of baskets should be varchar instead of integer
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43118 Bug ID: 43118 Summary: library_id in List of baskets should be varchar instead of integer Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- branchcodes are VARCHAR and not integers https://api.koha-community.org/#tag/baskets/operation/listBaskets in the moment: library_id | integer or null | Library the basket belongs to error when calling the API: message "Expected integer/null - got string." path "/body/0/library_id" status 500 example: api/v1/acquisitions/baskets?q={"basket_id":1} Test plan: Go to /cgi-bin/koha/acqui/basket.pl?basketno=1 Enter a Managing library then call the API: api/v1/acquisitions/baskets?q={"basket_id":1} --> Error 500 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 42501] New: ILL: The language of requests send to partners should be the preferred language used by libraries, not by patrons
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42501 Bug ID: 42501 Summary: ILL: The language of requests send to partners should be the preferred language used by libraries, not by patrons Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: piia.semenoff(a)ouka.fi QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com When sending a ILL-request to another library (in the ILL requests-module) the language of the request-email is formed from patrons preferred language and not by preferred language used by the partner library. I think it would be easier if it would work like this: If you order an inter library loan from a Finnish university library for an English-speaking patron, the base of the ILL_PARTNER_REQ -notice to the library would be in Finnish, according to the preferred language of the Finnish university library. The request would not be using the language used by the patron. Would it be possible to use partner library's preferred language in the ILL_PARTNER_REQ -notices (and not patrons)? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37195] New: Add ILL as option to TrackLastPatronActivityTriggers
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37195 Bug ID: 37195 Summary: Add ILL as option to TrackLastPatronActivityTriggers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com This has a couple of tricky aspects to it, I think. Basically, the problem is that for some patrons their only activity in the library could be to request article copies/prints through ILL. At least the way it works in Sweden, with ILL based around Libris, an ILL reques for a book would update lastseen, when the book is issued to the patron. But a request for an article copy/print would not update lastseen, because the ILL is just handled in the Libris backend, and there is no loan or other activity that is tracked today. The solution is probably to update lastseen from the Libris backend when a copy/print is marked as received, like so: $patron->update_lastseen('activity'); But that "activity" needs to be activated in TrackLastPatronActivityTriggers. Questions: - Should we add a generic "ill" activity? Or would it make sense to have e.g. "ill_loan" and "ill_copy"? - Would it be OK to have "ill" listed as an activity for TrackLastPatronActivityTriggers even if the ILL module is not activated? - Would it make sense to have an activity in TrackLastPatronActivityTriggers that perhaps does nothing out of the box, but relies on the different backends to actually call update_lastseen? Or could the ILL module itself call update_lastseen, and not rely on the backends to do it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 34776] New: Patron messaging preferences are lost when an error occurs during new account creation
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34776 Bug ID: 34776 Summary: Patron messaging preferences are lost when an error occurs during new account creation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1. Create a new account but cause an error that will keep the account from saving (enter the wrong age for a category or give the patron a username that's already being used) 2. Set some patron messaging preferences 3. Try to save the account and wait for the "The following fields are wrong. Please fix them." message 4. Note that the patron messaging preference selections are gone and you need to re-select them Note, this depends on the EnhancedMessagingPreferences system preference to be enabled This is similar to Bug 26558 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56