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

[Bug 23002] New: OPAC doesn't hold search filters in results pages
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '21

17 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23002 Bug ID: 23002 Summary: OPAC doesn't hold search filters in results pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 90166 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=90166&action=ed… image 1 Hi, We observed that if we place a link in OPAC leading to a search results (to see monthly's new additions for exemple) and we add another filter on these results (available to borrow for exemple, see image 1 with 76 results), when we are consulting the results pages, the OPAC will not hold the 2nd filter and will return to the maximum results for the 1st filter (new items in this this case, see image 2 with 111 results). This is occurring at the moment we are changing page in results. This bug is a little bit confusing for users. Thanks for the help, Alexandre -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 18170] New: Show damaged status on check-in
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '21

17 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18170 Bug ID: 18170 Summary: Show damaged status on check-in Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be nice if when checking in an item we could see if it has a damaged status without opening a new tab to see. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 20533] New: Call Number Search plugin functionality
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '21

17 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20533 Bug ID: 20533 Summary: Call Number Search plugin functionality Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The call number search plugin has great functionality- it would be great to get a little bit more features with this. There is no scrolling feature or the ability to look at the next page of results, so it would be nice to de-dup on the call number. Then the same call number is not repeated over and over again and then more unique call numbers can be displayed. In addition, if more than one title has the same call number, it is not helpful to see that multiple times in this search also. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20532] New: Display of 245 fields in basket.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '21

17 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20532 Bug ID: 20532 Summary: Display of 245 fields in basket.pl Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, when adding an item to a basket and viewing the basket.pl, only certain fields are visible (245a is the only field from the title) on this page. It would be beneficial to see the entire 245 field including all the subfields to the 245 fields on this page. This would help to know more specifically what format is being ordered. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 24132] New: search_with_library_limits vs filter_by_branch_limitations
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '21

16 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24132 Bug ID: 24132 Summary: search_with_library_limits vs filter_by_branch_limitations Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20443 Aside from the naming of these two subroutines (implemented at different times), Koha::Patron::Attribute::Types->search_with_library_limits and Koha::Patron::Attributes->filter_by_branch_limitations looks similar and that the code must be simplified. The join table is between borrower_attribute_types and branches (borrower_attribute_types_branches). So Koha::Patron::Attribute::Types can inherit directly from Koha::Objects::Limit::Library, not Koha::Patron::Attributes There are a couple of ways to deal with that: 1. Improve Koha::Objects::Limit::Library => Sounds wrong as there is no join table between borrower_attributes and branches 2. Remove Koha::Patron::Attributes->filter_by_branch_limitations and replace it by something like: my $attribute_types = Koha::Patron::Attribute::Types ->search_with_library_limits; my $attribute = $patron->extended_attributes ->search({ code => { -in => attribute_types->column('code') } }); Which sounds more correct. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20443 [Bug 20443] Move C4::Members::Attributes to Koha namespace -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

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