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

[Bug 29849] New: Add ability to dismiss fund warning for a session
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29849 Bug ID: 29849 Summary: Add ability to dismiss fund warning for a session 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When setting up a fund, one can provide an amount and/or percentage of money expended beyond which to warn the user. Once that limit has been exceeded, all subsequent orders against that will generate a warning. It would be helpful to be able to dismiss this warning and have Koha remember that for the session, so subsequent orders against the same fund do not repeat the message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26077] New: Batch Item Deletion Error Occurring Frequently with more than 5, 000 records
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26077 Bug ID: 26077 Summary: Batch Item Deletion Error Occurring Frequently with more than 5,000 records Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Submitting in response to an internal ticket from a library partner. We experience time out error messages when using the the batch item delete tool. Basically when attempting to delete anything more than approx 5,000 records. This has happen in the past and we were recently upgraded to 19.11. Can you adjust for us to have the ability to batch delete on a larger scale? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24793] New: TinyMCE for HTML notices
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24793 Bug ID: 24793 Summary: TinyMCE for HTML notices 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: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, what do you think about TinyMCE editor for HTML notices? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31128] New: REST API item not_for_loan_status doesn't respect biblio level fallbacks
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '23

06 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31128 Bug ID: 31128 Summary: REST API item not_for_loan_status doesn't respect biblio level fallbacks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com Outside of the UI, the not for loan status is coded to fallback to biblio level not for loan settings if the item is found to be loanable at the item level. We should respect that in the API too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 28658] New: With SearchMyLibraryFirst if library isn't set for the opac, try to guess it by checking branchip
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '23

04 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28658 Bug ID: 28658 Summary: With SearchMyLibraryFirst if library isn't set for the opac, try to guess it by checking branchip Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org If the SearchMyLibraryFirst syspref is set, the OPAC uses the logged in users branchcode to limit searches to their library. If it's an anonymous session that doesn't happen. This tries to guess the client library by checking for the client ip address in each libraries branchip setting. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 25631] New: Adding ability to alter the expiration date of the hold from the Patron's Account
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25631 Bug ID: 25631 Summary: Adding ability to alter the expiration date of the hold from the Patron's Account Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, for a hold expiration date to be changed, it would need to happen from the Item's Record (Hold), or the patron themselves can edit/add an expiration date. It would be nice to be able to add/edit an expiration date to the patron's hold from their Holds Summary on the Patron detail page. members/moremember.pl circ/circulation.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 27311] New: Don't pass borrowernumber to check_password plugin hook
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27311 Bug ID: 27311 Summary: Don't pass borrowernumber to check_password plugin hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org check_password is implemented in two places: 1. In Koha::Patron::set_password https://git.koha-community.org/Koha-community/Koha/src/branch/master/Koha/P… 2. In Koha::Patron::store https://git.koha-community.org/Koha-community/Koha/src/branch/master/Koha/P… The call to the plugin inside Koha::Patron::store comes before this line: $self = $self->SUPER::store; which means there is not yet a borrowernumber to pass to the plugin, and this never worked. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 26247] New: Search terms retained in header search creates system inconsistency
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26247 Bug ID: 26247 Summary: Search terms retained in header search creates system inconsistency Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you type "test" in "Search the catalog" and click "Submit", the search term will be retained in the box. This means if you do a search and then want to scan a barcode into "Check out", "Check in", or "Renew", you first have to manually clear the search terms. This is inconsistent with how the header search boxes work overall. For instance, if you do a "Check out", it doesn't retain the value used to search. Either the search terms shouldn't be retained after a catalog search (change introduced in Bug 19046), or the text shouldn't be copied from that tab to other tabs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 75

[Bug 31500] New: Add ability to specify MaxReservesPickupDelay at the patron category level
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31500 Bug ID: 31500 Summary: Add ability to specify MaxReservesPickupDelay at the patron category level 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would like to be able to override MaxReservesPickupDelay on a per category basis. A good use case for this is that some libraries have a special patron category for patrons that are from "out of town" on vacation. In this case, the library may want to specify a shorter pickup period before the item expires than they would for a patron that lives in the area. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 29415] New: Wrong number of received items/quantity shown in several places
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '23

03 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29415 Bug ID: 29415 Summary: Wrong number of received items/quantity shown in several places Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For standing orders there is something not correct with the way the number of items received is calculated. A Order 1) Create a basket as standing order 2) Create an order for any record in your catalog 3) Verify quantity is 1 (always for standing orders) B Receive 1) Receive shipment for your order 2) Make sure to change quantity received to something higher than 1 3) Finish receiving C Verify display 1) Search for your invoice on the invoices page 2) Verify it shows quantity received as entered 3) Got to invoice details page /cgi-bin/koha/acqui/invoice.pl?invoiceid=1 4) Verify it still shows 1 as quantity - should show the received quantity 5) Click on the record's title to go to the detail page 6) Switch to acquistion detail tab 7) Verify it shows 1 too - should differentiate between ordered/received I think the first (invoice) is clearly a bug, the second might be seen as a display error, but we should specify which quantity is shown and possibly add a display for ordered / received. If the status is received the info on the acq tab is definitely misleading. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5