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

[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 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 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

[Bug 29698] New: items are not available for TT syntax for PREDUEDGST
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29698 Bug ID: 29698 Summary: items are not available for TT syntax for PREDUEDGST Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 27346] New: C4::XISBN warning on hash
by bugzilla-daemon＠bugs.koha-community.org 08 May '26

08 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27346 Bug ID: 27346 Summary: C4::XISBN warning on hash Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using ThingISBN alone you get a warning : Failed Can't use string ("1") as a HASH ref while "strict refs" in use at /home/koha/src/C4/XISBN.pm line 99. sub get_xisbns { my ( $isbn, $biblionumber ) = @_; my ($response,$thing_response,$syndetics_response,$errors); ... $response->{isbn} = [ @{ $syndetics_response->{isbn} or [] }, @{ $thing_response->{isbn} or [] } ]; Vars $thing_response,$syndetics_response must be initialised as an hashref. Or maybe rewrite a bit this code. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41101] New: Allow extended patron attribute to be non-editable in the staff interface.
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41101 Bug ID: 41101 Summary: Allow extended patron attribute to be non-editable in the staff interface. Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cj.lynce(a)westlakelibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com It would be helpful to have a selectable option for extended patron attributes to be non-editable in the staff interface, but still be show to staff. The current options only allow to make an extended attribute editable/non-editable in the OPAC. For example, an extended patron attribute is utilized by our materials recovery service plugin (Unique Management Services - Gentle Nudge) to track if a patron is or is not in a recovery status. The plugin handles changing of the attribute automatically, and staff editing the attribute manually causes issues with the plugin processes. Staff still need to see if the patron is in a recovery status, but should not be able to change it themselves. Getting into more specifics, I could see 'superlibrarian's being able to change the status to correct certain issues with the plugin, but not most staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 21627] New: System preference for recipient emails of gather_print_notices.pl
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21627 Bug ID: 21627 Summary: System preference for recipient emails of gather_print_notices.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I think it would be nice if the librarians without shell access to the server could change the email address list that the gather_print_notices.pl cronjob uses to send emails to. Now the only way is to specify the --email option when running the script. I suggest a system preference for this that would have a comma separated list of emails. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23