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

[Bug 18195] New: Charge for expired holds per patron category
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '21

15 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18195 Bug ID: 18195 Summary: Charge for expired holds per patron category Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com ExpireReservesMaxPickUpDelayCharge allows one charge to be applied to all holds that expire. However, each patron category can have a unique hold fee. It would be preferable if each patron category could also have a unique 'hold expired' fee, so different patron categories could be charged different amounts (or not at all) for expired holds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26523] New: In reserve/request.pl biblioitemnumber is used where biblionumber is required.
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '21

15 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26523 Bug ID: 26523 Summary: In reserve/request.pl biblioitemnumber is used where biblionumber is required. Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the fix of bug 24185, (commit 18ad5f5eea8aab8414783f4b75408cfebd2518da) bibliotemnumber is used where biblionumber is required. The consequence is that ItemsAnyAvailableAndNotRestricted is called on the wrong record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 26429] New: If a waiting hold has expired (date has passed)- looking at the request.pl page, the expiration date is for tomorrow
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '21

13 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26429 Bug ID: 26429 Summary: If a waiting hold has expired (date has passed)- looking at the request.pl page, the expiration date is for tomorrow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 To recreate: 1. Have a waiting hold - the expiration date of 9/9/2020. 2. Reserve table shows 9/9, request.pl shows 9/9 3. Fast forward to 9/10 4. If library is not expiring holds, this hold expiration date will now show the expiration date of 9/11 on the request.pl page. 5. The reserve table still shows the 9/9 date. It would appear that since the date picker (from the reserves.pl page) can not show dates in the past or even for the current date, it will show the next available date. This is confusing! This bug seems very relevant to the bug I am filing: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21147 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 25789] New: New expiration date editor on request.pl can set a date in the past
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '21

09 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25789 Bug ID: 25789 Summary: New expiration date editor on request.pl can set a date in the past Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When creating a new request on request.pl, staff cannot set a hold expires on date in the past -- input name="expiration_date". When editing an existing request, however, the new datepicker for editing the expiration date on request.pl does allow for a date to be set in the past -- input name="expirationdate". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 27008] New: Broken SQL statement formed in Breeding.pm
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '21

09 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27008 Bug ID: 27008 Summary: Broken SQL statement formed in Breeding.pm 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: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org The C4/Breeding.pm code doesn't properly form SQL statements and gives error instead: > DBD::mysql::st execute failed: You have an error in your SQL syntax; check the > manual that corresponds to your MariaDB server version for the right syntax to > use near '' at line 5 [for Statement "SELECT import_record_id, file_name, isbn, > title, author > FROM import_biblios > JOIN import_records USING (import_record_id) > JOIN import_batches USING (import_batch_id) > WHERE "] at /usr/share/koha/lib/C4/Breeding.pm line 100. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 26338] New: Show tool plugins run in tools home
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '21

07 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26338 Bug ID: 26338 Summary: Show tool plugins run in tools home 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In tools home there is a link to the table showing tool plugins. Would be great to be able to run a tool plugin directly from tools home. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 25287] New: Add columns_settings support to API datatables wrapper
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '21

06 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25287 Bug ID: 25287 Summary: Add columns_settings support to API datatables wrapper Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In order to use the API wrapper for datatables, we need to add the option to set columns settings to it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 17388] New: Suggestion detail page marks suggestion as rejected and accepted
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '21

06 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17388 Bug ID: 17388 Summary: Suggestion detail page marks suggestion as rejected and accepted 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org To reproduce: - Create a suggestion - In suggestions management, mark it ("accidentally") as accepted. - Then change status, e.g. to rejected - Display the suggestion's detail page Result: Weird information on detail page, suggestion appears as rejected and as accepted. See screeshot. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26898] New: Notify new manager when updating suggestions from suggestions homepage
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '21

06 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26898 Bug ID: 26898 Summary: Notify new manager when updating suggestions from suggestions homepage 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 Depends on: 23590 When changing the manager of one or more purchase suggestions from suggetion.pl, there's no mechanism for sending a notice to the new manager, as one can do when editing a single suggestion. We should be able to send notice(s) in either interface. If setting multiple suggestions to one manager in bulk, should that be multiple individual notices? Or one digest notice? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23590 [Bug 23590] Add the ability to change the manager of a suggestion and notify the new manager -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24451] New: Clarify wording when deleting a bib attached to orders
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '21

06 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24451 Bug ID: 24451 Summary: Clarify wording when deleting a bib attached to orders 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl >From detail.pl, when attempting to delete a bib that is connected to any uncanceled orders in acquisitions, we receive the message: "Warning: This record is used in X order(s). Deleting it could cause serious issues on acquisition module. Are you sure you want to delete this record?" This message would be more helpful if it distinguished between open and closed orders. Deleting a bib connected to an open order will cause serious issues. Deleting a bib connected to closed orders will not. I see three possible fixes: - Change the message to specify "This record is used in X open order(s) and Y closed order(s). Deleting a record used in open orders could cause serious issues ..." - Change the message to only appear if the bib is used in orders connected to an active budget and give a count of only orders connected to an active budget. - Complete bug 16872 to entirely block the deletion of bibs in open orders, then remove this warning. If we're not allowing the deletion of bibs from open orders, then it's not a big deal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2