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

[Bug 26005] New: OPAC cart display fails with error
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '21

06 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26005 Bug ID: 26005 Summary: OPAC cart display fails with error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: critical Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: aleisha(a)catalyst.net.nz, david(a)davidnind.com, jonathan.druart(a)bugs.koha-community.org, lucas(a)bywatersolutions.com, testopia(a)bugs.koha-community.org Depends on: 25402 Bug 25402 was supposed to have depended on Bug 5087 but somehow that got missed during QA. The result is that the OPAC cart is completely broken, giving this error when the cart window is opened: DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'opac_option' in 'where clause' at /kohadevbox/koha/Koha/Objects.pm line 144 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25402 [Bug 25402] Put OPAC cart download options into dropdown menu -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 24225] New: Add Koha::Objects->search_from_api method
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '21

05 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24225 Bug ID: 24225 Summary: Add Koha::Objects->search_from_api method 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 Bug 23843 introduced the Koha::Object(s)->to_api method and the attribute mappings on the Koha::Object classes. Bug 23893 will introduce the reverse mapping along with the Koha::Object->new_from_api and Koha::Object->set_from_api methods. So all the pieces are set so we can properly build a Koha::Objects->search_from_api method that does something similar to the objects.search helper, but uses the classes' mappings instead of requiring the to_api and to_model methods to be passed. This will ultimately help clean all the controllers and (hopefully) improve productivity re: adding endpoints, because of the removal of that intrinsic complexity both on controllers, and tests. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 19207] New: Don't export fields
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '21

03 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19207 Bug ID: 19207 Summary: Don't export fields Change sponsored?: --- Product: Koha Version: 3.22 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: osimandias(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 66613 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66613&action=ed… srceenshot GUI option In the GUI option "Don't export fields" (of export.pl) is not expressed correctly. It does not exclude the field of the exported records, What it does, is to exclude the records that contain that field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 16628] New: Patrons requesting modifications link behaves differently on the home page than the members-home.pl page
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '21

02 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16628 Bug ID: 16628 Summary: Patrons requesting modifications link behaves differently on the home page than the members-home.pl page Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 It would appear that the links do not behave the same between the members-update.pl page and mainpage.pl. When IndependentBranchesPatronModifications is set to Prevent, the link on mainpage.pl shows the count for your library, and only shows when your library has requests. However, the link ALWAYS shows on members-update.pl, and shows the total of all requests. I don't believe any other feature in Koha works this way, and I don't believe this should be the behavior of this feature. In my opinion, the link on mainpage.pl behaves correctly, and the link on members-update.pl should be changed to do the same. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25708] New: [OMNIBUS] Use allow/disallow terminology in code
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '21

02 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25708 Bug ID: 25708 Summary: [OMNIBUS] Use allow/disallow terminology in code 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Allow/disallow terminology is preferable to whitelist/blacklist https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white. https://www.clockwork.com/news/creating-inclusive-naming-conventions-in-tec… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3