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

[Bug 41477] New: Show barcode of item in the action logs
by bugzilla-daemon＠bugs.koha-community.org 09 May '26

09 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41477 Bug ID: 41477 Summary: Show barcode of item in the action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently when displaying an item in the log viewer for 'cataloguing' modifications we display text/link like: Item 972 from Bibliographic record 438 Librarians tend to use the barcode as the unique ID of the record, and we should display this info so they can more easily identify the items. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 27859] New: Marc export for search result
by bugzilla-daemon＠bugs.koha-community.org 09 May '26

09 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27859 Bug ID: 27859 Summary: Marc export for search result 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 This patch provides the option of exporting a search result as MARCXML or iso 2709. Ideally the export should be asynchronous but it was much trickier than first thought to fork and detach from Apache so gave that up for now. A link to the export is sent to the current user as an email as a simple way of delivering the response asynchronously (keeping it this way so don't have to refactor when/if the export is made asynchronous). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 90

[Bug 41169] New: Cancelling order from a basket doesn't warn about removing items
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41169 Bug ID: 41169 Summary: Cancelling order from a basket doesn't warn about removing items Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mikko.liimatainen(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org When cancelling an order in a basket there is no warning about item deletion. This can be a problem if the item is already in circulation. If the items attached to the order can not be removed, this is given a notification as the order has been cancelled. When you are cancelling an order you get a confirmation page with this text: "Are you sure you want to cancel this order (45) Bibliographic record will not be deleted." I'd like there to be a mention that the items of this order will be deleted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 40968] New: 'Edit this search' forgets about 'whole_records' and 'weighted_fields'
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40968 Bug ID: 40968 Summary: 'Edit this search' forgets about 'whole_records' and 'weighted_fields' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Found it while playing with links on bug 40966. To reproduce: 1. Apply bug 40966 2. Perform an adv search as in that bug. Using the 'More options' tab. 3. Include any of the following options (or both): * Search entire MARC record * Apply field weights to search 4. Notice the facets include 'whole_records=1' and/or 'weighted_fields=1' (this is the bug 40966 patch in action) 5. hover the 'Edit this search' link => SUCCESS: It gets the query parameters passed through 6. Click on the link => FAIL: None is really set, we lost search information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 39934] New: Standard backend shows attributes from previously "migrated from" backends
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39934 Bug ID: 39934 Summary: Standard backend shows attributes from previously "migrated from" backends Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)openfifth.co.uk Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 40646] New: ‘Patron account expiry’ message selections un-set when switching 'Enforce patron account expiry notice' from Yes to No
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40646 Bug ID: 40646 Summary: ‘Patron account expiry’ message selections un-set when switching 'Enforce patron account expiry notice' from Yes to No Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com With 30301, the ‘Patron account expiry’ message line doesn't show in 'Default messaging preferences for this patron category' if 'Enforce patron account expiry notice' is set to Yes. This means that if the notice is being enforced and the library needs to edit its default preferences, they have to switch 'Enforce patron account expiry notice' to No, click Save, and then open the category back up for editing. However, switching 'Enforce patron account expiry notice' from Yes to No un-sets the existing preferences rather than just showing existing selections for editing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 30300] New: Add patron expiration email to patron messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30300 Bug ID: 30300 Summary: Add patron expiration email to patron messaging preferences 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This enhancement will add a messaging preference for patron expiration notices, and adjust the cronjob that sends these notices to obey the patrons preference -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 29612] New: Orders By Fund report (orders_by_fund.pl) should include actual cost (unitprice)
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29612 Bug ID: 29612 Summary: Orders By Fund report (orders_by_fund.pl) should include actual cost (unitprice) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The built-in Orders by Fund report does not include the actual cost for orders than have been received. It only shows the vendor price and the estimated purchase price. We should add two new columns to show both the actual cost per item and the total actual cost (unitprice * quantity). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39376] New: Adding Lists in the staff interface should require permissions for public and private
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39376 Bug ID: 39376 Summary: Adding Lists in the staff interface should require permissions for public and private Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl At the moment, any staff user can create public and private lists - without any specific "Lists" permissions. There should be 2 new permissions "create_public_lists" and "create_private_lists". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 23936] New: Authenticating a patron without library card or ID
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23936 Bug ID: 23936 Summary: Authenticating a patron without library card or ID Change sponsored?: --- Product: Koha Version: 18.11 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 A staff member had an idea. Once in a while we have a patron come through that does not have ID or library card with them (maybe jogging or biking or such). What if we could bring up their account, and if they have an SMS number set, we could click a button on their account, and it texts them a random code, and that code also shows on the patron screen (that goes away when you navigate away from the page). Maybe this could be a good alternative? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6