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

[Bug 34681] New: Last borrower and last/previous borrower doesn't display if borrower cardnumber is empty
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34681 Bug ID: 34681 Summary: Last borrower and last/previous borrower doesn't display if borrower cardnumber is empty Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: Have StoreLastBorrower enabled to store Last Returned By. Create account and leave cardnumber empty. Check out and return item with that account. Go to items detail page. See that Last Returned By and, if return is not anonymized, Last Borrower appears blank (you can inspect the fields and see that borrower information is there but not visible). Previous borrower will similarly be blank if it is from an account with no cardnumber. Most libraries will usually have a value in cardnumber, but if they don't for any reason, perhaps for in-house cards or by user error, it hides important circ information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 35246] New: REST API: api/v1/biblios crashes with accept header application/json
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35246 Bug ID: 35246 Summary: REST API: api/v1/biblios crashes with accept header application/json Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: tomascohen(a)gmail.com See also bug 33960. Found it testing there. [2023/11/03 10:33:00] [ERROR] GET /api/v1/biblios: unhandled exception (Mojo::Exception)<<Can't call method "to_api" on an undefined value at /usr/share/koha/Koha/Biblio.pm line 1433.>> => my $json_biblioitem = $self->biblioitem->to_api( $args ); Just testing /api/v1/biblios with Accept=application/json. Note that Accept=application/marc works fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34127] New: Allow to customize CSV export of basketgroup and add a ODS export
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34127 Bug ID: 34127 Summary: Allow to customize CSV export of basketgroup and add a ODS export Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The CSV export of basketgroup is currently not customizable A customizable ODS export should also be useful -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36155] New: Improve perfs of suggestion.pl when there are many budgets
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36155 Bug ID: 36155 Summary: Improve perfs of suggestion.pl when there are many budgets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Page suggestion/suggestion.pl always calls GetBudgets() and GetBudgetHierarchy(). But the result are not always used in template. When there are many budgets and funds this takes some time. Also CanUserUseBudget() in a loop should use a unique Koha::Patron object of the logged in user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 32950] New: marc modification template moving subfield can lose values for repeatable fields
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32950 Bug ID: 32950 Summary: marc modification template moving subfield can lose values for repeatable fields Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 146586 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=146586&action=e… mrc with multiple 020 fields including 020$z Moving one subfield to another fails for repeatable fields where the field to be moved doesn't exist in the first instance 1. Make marcmodtemplate as follows a. Move every 020 z field to field 020 a 2. Stage marc exchange file (attached) with following in 020 field (note only 7th and 8th have 020z and these are the ones we wish to move to subfield a) =020 \\$a9781003182870$q(ebk) =020 \\$a1003182879 =020 \\$a9781000407204$q(electronic bk. : EPUB) =020 \\$a1000407209$q(electronic bk. : EPUB) =020 \\$a9781000407167$q(electronic bk. : PDF) =020 \\$a1000407160$q(electronic bk. : PDF) =020 \\$z9781032023175$q(hbk.) =020 \\$z9780367760380$q(pbk.) 3. view staged record and observe fields 020 subfield a fields have all gone and subfield z has not been moved, but its value removed: 020 _a _q(ebk) 020 _a 020 _a _q(electronic bk. : EPUB) 020 _a _q(electronic bk. : EPUB) 020 _a _q(electronic bk. : PDF) 020 _a _q(electronic bk. : PDF) 020 _q(hbk.) _a 020 _q(pbk.) _a Note, adding a conditional to marcmodtemplate "only do this if 020 z subfield exists makes no difference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 33856] New: Inventory tool CSV export contains untranslatable strings
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33856 Bug ID: 33856 Summary: Inventory tool CSV export contains untranslatable strings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 22135 The "Problem" header row label and the problems themselves are untranslatable as they are added in the inventory.pl file. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22135 [Bug 22135] Inventory tool doesn't export "out of order" problem to CSV -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 35700] New: Holds reminder cronjob --triggered switch does not work as intended if the day to send notice hits concurrent holidays
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35700 Bug ID: 35700 Summary: Holds reminder cronjob --triggered switch does not work as intended if the day to send notice hits concurrent holidays Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz If the calendar has concurrent holidays, when holds_reminder.pl cronjob is being ran daily with the --triggered switch and the day the notice should be sent lands on a holiday which is repeated the following days, the cronjob sends holds reminders until the holiday period ends. To reproduce: Reserve an item, receive it at a branch where the reserve was made to. Move the waitingdate and reservedate of the reserve to x days before the reserve was made in the database. Add holidays (single non-repeated days) to the calendar so that the first holiday lands on a date when the hold reminder should be sent. Set up the cronjob to run so that the --days trigger matches the first added holiday using also the --triggered switch: holds_reminder.pl -v --days x --triggered --holidays -c for example. Check that the x:th day from the reserve's waitingdate is a holiday, and the date has following days set as holidays as well. Notice that on the following day/days of the first sent reminder, the message is sent again. Same happens the following holidays. It seems the notice is sent also if there is a repeated holiday following the first single day holiday the message was sent (like if saturdays and sundays were repeated holidays). I guess this could be reproduced easier by moving your system date forward and running the cronscript again. I couldn't reproduce the same bug when moving back the waitingdate of the reserve to simulate a day had passed since the first message for some reason. Notice that modifying the holidays use a cache, so just making changes to the database is not enough for the cronscript to notice the changes made. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 31460] New: Merging Item Groups Loses Groups
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31460 Bug ID: 31460 Summary: Merging Item Groups Loses Groups 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl With the new feature of Item Groups, if a library merges two records together, both having Items with Item Groups attached, the merge will only retain the Item Group on the Kept Record. It would be beneficial to libraries that all item information including groups is retained in a merge. Test: 1. Have a record (A) with 3 items. 2. Create an item group with 2 of these items. 3. Have a second record (B) with 4 items 4. Create an item group with 2 of these items. 5. Merge the two records together keeping record A 6. Results will show that all items are moved over to record A, but the item group from record B, is not there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25015] New: Staff with Edit Items permission Currently Can Not Edit Items attached to a Fast Add Framework
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25015 Bug ID: 25015 Summary: Staff with Edit Items permission Currently Can Not Edit Items attached to a Fast Add Framework Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If a staff has the permission has only the permission in Cataloging to "Edit Items" currently, they can't edit items attached to a Fast Add bib. What should the change be? Does a staff member need to have Fast Cataloging and Edit Items to be able to Edit Items attached to a Fast Added Bib? And if that is the case, the bug lies with the fact the staff member doesn't know that this bib is a Fast Add bib- the Edit option should not be visible to staff that only have "edit items" and not "Fast Cataloging" Or Is it a library's understanding that the permission "Edit Items" allows All Items can be edited even the items attached to Fast Add Biblios? And if that is the case, then the change lies with how the permissions are coded in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 25947] New: Improve locked account message
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25947 Bug ID: 25947 Summary: Improve locked account message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 106643 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106643&action=e… Warning messages in the patron details When using FailedLoginAttempts, a patron's account is blocked after X many failed login attempts on the OPAC. When that happens, a message 'Account has been locked.' appears on the patron account details page. This message does not indicate why or how it was blocked. I suggest we change it to 'Account has been locked due to too many failed login attempts'. Furthermore, the font is dark red whereas the font for other warnings (such as wrong category or unpaid fines) is bright red and bold. To test: 1. Change FailedLoginAttempts to a small number, like 2 2. Go to a patron's account and copy their username (while you're there, change the password and add some fines, too) 3. In the OPAC, try to log in with the username and a wrong password several times 4. Go back to the patron's account in the staff interface 5. Note that there is no indication as to why the patron's account is locked and that the font color and weight does not match the other warnings. Also, there is no button to change the password next to the warning. When a patron has unpaid fines or is in the wrong category, there is a button to either pay/writeoff the fines or change the category next to the warning. I would add a button that says 'Change password' next to the locked account warning. This might be outside the scope of this bug, but I think it would improve usability. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 75