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

[Bug 27696] New: Allow choice between ISSUESLIP and ISSUEQSLIP when printing a SCO receipt
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27696 Bug ID: 27696 Summary: Allow choice between ISSUESLIP and ISSUEQSLIP when printing a SCO receipt 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries like to print the issue quick slip from the SCO page, others like to print the regular issue slip here. We should allow for librarians to choose which one they'd like their patrons to get. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 20161] New: Show same information for format, material type etc. on the detail page as in the result list
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20161 Bug ID: 20161 Summary: Show same information for format, material type etc. on the detail page as in the result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org A lot of libraries ask, why there is less information about the material type, format and literary format shown on the detail page than in the result list. I suggest to match both displays and make it possible to hide with CSS as you can already do on the result list (using the same classes). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 31009] New: Claims list take too much times (timeout when you have so many claims) on serials
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31009 Bug ID: 31009 Summary: Claims list take too much times (timeout when you have so many claims) on serials Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org To view claims, when clicked, an SQL query is performed to search for claims by vendor and build a select list. If you have so many claims, it takes too long or even creates a timeout problem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 40886] New: Patron circ messages not sorted in chronological order
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '25

29 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40886 Bug ID: 40886 Summary: Patron circ messages not sorted in chronological order Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com When viewing patron messages in the staff interface (e.g., on the circulation page), messages are currently ordered by message_type only. This causes them to display out of chronological order, making it difficult for staff to quickly identify the most recent messages. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 36633] New: Support anti-the at REST API level
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '25

29 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36633 Bug ID: 36633 Summary: Support anti-the at REST API level Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com CC: tomascohen(a)gmail.com Coming from bug 35560. If we migrate UI tables to DT using the REST API we need support the anti-the sorting type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40417] New: Search_rs is re-instating deleted query parameters
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '25

29 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40417 Bug ID: 40417 Summary: Search_rs is re-instating deleted query parameters Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Any endpoint that is calling $c->objects->search after calling $c->req->params->remove('param_name') is having that parameter reinstated to the search object -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 27691] New: allow HTML in Notes output on guided_reports_start.tt
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '25

29 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27691 Bug ID: 27691 Summary: allow HTML in Notes output on guided_reports_start.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some reports have a long and detailed notes section pertaining to a given report. With the html filter it can be very difficult to parse out those notes. Is there any reason we cannot use a $raw filter in this situation? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 37666] New: Make additional fields available via Template Toolkit in notices
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '25

29 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37666 Bug ID: 37666 Summary: Make additional fields available via Template Toolkit in notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It seems that is not possible today (or in a complex way?) to display in notices information stored in additional fields defined in admin/additional-fields.pl It could be nice to add this feature, in the same spirit as https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 40918] New: Invoice Adjustment Reason always "No reason" even if report shows a saved reason
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40918 Bug ID: 40918 Summary: Invoice Adjustment Reason always "No reason" even if report shows a saved reason Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Go to Acquisition. 2. Create a vendor. 3. Click "Receive Shipment" 4. Enter an invoice number and save. 5. Go to Administration->Authorized Values->Add A Category 6. Name it ADJ_REASON 7. Put in 2 options 8. Go to invoices in Aqusition 9. Add an adjustment (enter an amount and select a reason, then save) 10. The reason is set to "no reason" 11. Go to reports 12. new sql report select * from aqinvoice_adjustments 13. Run the report and see your reason is saved. 14. go back to the invoice and click save adjustments 15. run the report again, see there's no longer a reason. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 40292] New: SQL syntax error when upgrading to 25.05 on MariaDB 10.3, RENAME COLUMN unsupported
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40292 Bug ID: 40292 Summary: SQL syntax error when upgrading to 25.05 on MariaDB 10.3, RENAME COLUMN unsupported Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Got this report on Mattermost for 25.05: Configurando koha-common (25.05.01-1) ... Upgrading database schema for biblio Upgrade to 24.12.00.042 [07:56:03]: Bug 39838 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39838) - Rename alias_id -> vendor_alias_id ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'COLUMN alias_id TO vendor_alias_id' at line 1 at /usr/share/koha/lib/C4/Installer.pm line 825 After investigation and confirmation, the usage of RENAME COLUMN is the problem. This syntax is unsupported in versions of MariaDB prior to 10.5.3, here's the relevant documentation for reference: mariadb dot com/docs/server/reference/sql-statements/data-definition/alter/alter-table#rename-column The solution is to fix the usage of RENAME COLUMN in the current db_revs and to write a coding guideline and a QA test to accompany it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 74