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

[Bug 40162] New: Point of Sale receipt option for email to include patron lookup for email address value
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '25

18 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40162 Bug ID: 40162 Summary: Point of Sale receipt option for email to include patron lookup for email address value Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk The Point of Sale receipt option to send to an email address is very useful. However, quite often the customer is already a registered user so an extra step for staff to manually type in the customer's email address when this information is already in the system. Staff would like to see a 'patron lookup' option for emailing a receipt in POS so they can find the user and attach with their email address field values to send the email to the customer. I can see some potential complications with this one personally as email addresses can be across multiple fields but as it is a popular one with our staff I have promised to raise a bugzilla for this enhancement suggestion. The workaround remains for the bill to be created on the customers account instead for which it is then easy to mail them a receipt from the transactions tab in their patron record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 34784] New: Add ability to populate empty item callnumbers for a record based on the itemcallnumber syspref
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '25

18 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34784 Bug ID: 34784 Summary: Add ability to populate empty item callnumbers for a record based on the itemcallnumber syspref 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries would like to auto-populate item callnumbers for items on a record based on the system preference "itemcallnumber". Only items with empty callnumbers would affected. This would add a button "Populate empty item callnumbers" on catalogue/detail.pl, as well as a "Populate callnumber" button for each line in the holdings table to set the callnumber for that specific item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 40152] New: CatalogerEmails system preference does not allow more than one email address
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '25

18 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40152 Bug ID: 40152 Summary: CatalogerEmails system preference does not allow more than one email address Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the Administration module, the CatalogerEmails system preference determines which email address/es are notified when a catalog concern is submitted. The Koha Manual says, "You can input more than one email address by separating them with commas." However, when multiple email addresses are entered, separated by a comma (or a comma and space), the changes will not save and "Please enter a valid email address" appears in red text. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 9598] Ability to split up shipping cost between all items and funds on an invoice
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9598 Catrina Berka <catrina(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |catrina(a)bywatersolutions.co | |m -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40157] New: OAI's CSS should be updated to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40157 Bug ID: 40157 Summary: OAI's CSS should be updated to Bootstrap 5 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The current files are dated (bootstrap 3) and contain http links to fonts which cause the OAI page to be displayed as insecure. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36600] New: Add ability to print an import report
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36600 Bug ID: 36600 Summary: Add ability to print an import report Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to have an option to print/export an import report. It could contain the information that appears on the screen and other useful types of information. For example bug 21272 reports a data error about mismatched library codes. Other data issues should be able to be retained and reported on as well. A report could include: Job ID File name Status Progress Type Start/End times The data in the table of number of records added, ignored, replaced matching rules used, framework assigned Data error messages - such as records rejected due to data issues (missing itypes, etc.) There are probably other things. It would be nice to be able to retain some of this data when trying to troubleshoot an import failure. Right now, some of the data is lost/buried once navigating away from the screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 29743] New: Importing bad MARC can cause internal server errors in Koha
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29743 Bug ID: 29743 Summary: Importing bad MARC can cause internal server errors in Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org MARC data can be imported into Koha that may be invalid and can cause internal server errors when someone attempts to view that records. We should validate MARC data before it is imported into the database to prevent this issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 15266] stage-marc-import.pl does not show warning messages on MARC error
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15266 Catrina Berka <catrina(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |catrina(a)bywatersolutions.co | |m -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15148] Serials: Test prediction pattern starts at First issue date, not Subscription start date
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '25

17 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15148 Arthur Suzuki <arthur.suzuki(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Patch doesn't apply --- Comment #15 from Arthur Suzuki <arthur.suzuki(a)biblibre.com> --- I've been trying to apply the patch but it doesn't apply anymore. I've also tried to rebase it but honestly I don't see a big difference between with the rebased patch and current master. I mean, I can't even reproduce the issue on current main now... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34063] New: items.paidfor haunting beyond the grave
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '25

16 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34063 Bug ID: 34063 Summary: items.paidfor haunting beyond the grave Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Depends on: 26268 Bug 26268 only drops the column items.paidfor if the column is empty. If there is a value, a warning message is displayed, but the database upgrade completes successfully. So you may end up with 47 columns in your items table in Koha 22.11 while the deleteditems table only has 46 columns. This will cause scripts like /cgi-bin/koha/reports/issues_stats.pl to bust with a 500 error since it can't do a * union on those two tables with a different number of columns. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26268 [Bug 26268] Remove items.paid for once and for all -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29