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

[Bug 24581] New: DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.privacy_guarantor_fines' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 92
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '20

27 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24581 Bug ID: 24581 Summary: DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.privacy_guarantor_fines' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 92 Change sponsored?: --- Product: Koha Version: 19.11 Hardware: HP OS: Linux Status: NEW Severity: blocker Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: rajofigueroa(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org In upgrading Koha I.L.S. from koha 19.05 to koha 19.10.2. I installe koha 19.10 en my laptop envy hp, in Debian 10 buster, and everything was ok. But whan I bring tried to change the new database with the old one , it give me that error mesage DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.privacy_guarantor_fines' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 92 An in the OPAC : Software error: Template process failed: undef error - DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.reset_password' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 269 Please some hep needed. Thanks a lot Lic. Ramon Figueroa, from caracas, Venezuea -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 25606] New: Adds "Remove all reserves" button to course details
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '20

27 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25606 Bug ID: 25606 Summary: Adds "Remove all reserves" button to course details Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: joe(a)flo.org QA Contact: testopia(a)bugs.koha-community.org Adds a "Remove all reserves" button to the course details screen for each course reserve. It allows for quick removal of courses with many reserve items attached. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 20833] New: Feature request: Better copy/paste for system preferences
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '20

25 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20833 Bug ID: 20833 Summary: Feature request: Better copy/paste for system preferences Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Sometimes it is useful to be able to copy and paste system preferences as text rather than screenshot -- the nature of the system preferences screen makes this very difficult to do, because often the most important text is the system preference values, which are either in a text box or labels in a drop down. For instance the system preference 'AcqCreateItem' has the text Create an item when [*] This is only the default behavior, and can be changed per-basket. Where [*] is a drop down containing one of the values. - placing an order. - receiving an order. - cataloging the record. A simple copy and paste of the 'Value' box gives "Create an item when This is only the default behavior, and can be changed per-basket."; there's no way to copy the values in the drop down. I would be nice to have a 'copy to clipboard' button that would copy the 'preference' and 'value' fields. For instance if AcqCreateItem was set to 'placing an order', the following text would be placed in the copy/paste buffer: AcqCreateItem: Create an item when [placing an order.] This is only the default behavior, and can be changed per-basket. If multiple system preferences show up in the 'Preference' field, they would be comma separated, e.g. LocalHoldsPriority, LocalHoldsPriorityPatronControl, LocalHoldsPriorityItemControl: [Don't give] priority for filling holds to patrons whose [pickup library] matches the item's [holding library] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 22199] New: Planning Budget does not retain values
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22199 Bug ID: 22199 Summary: Planning Budget does not retain values Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When trying to use the planning function in Acquisitions/Budgets, Koha does not retain the values entered for month/itemtype/library, when entered either manually, using autofill, or a combination of both. Once figures have been entered and save is clicked, all the figures revert to zero. Noticed in 18.05.07 and confirmed in 18.11.00. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 23937] New: Clear filter in Acquisitions Search doesn't work
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23937 Bug ID: 23937 Summary: Clear filter in Acquisitions Search doesn't work Change sponsored?: --- Product: Koha Version: 19.05 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 Created attachment 94927 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94927&action=ed… search With the introduction of bug 21308, the library can search the acquisitions module for a title, order, etc. With this first acquisition search, the results will populate and all the search filters appear on the left-hand side of the screen. If the search started in the standard acquisitions search -see screenshot- then the clear filter does not work when the results are populated. The only way to clear this search is to search for something else using the left hand search boxes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 23820] New: Club Hold pickup locations should be able to default to patron's home branch
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23820 Bug ID: 23820 Summary: Club Hold pickup locations should be able to default to patron's home branch 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: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently club holds force you to choose a single, specific pickup location when placing holds for the club. This isn't ideal in a multibranch/consortial setting. It would be nice if there were an option to default the pickup location to the patron's home branch for holds placed with clubs. My use case involves clubs for specific authors. For example, I want to create a 'Stuart Woods' club that patrons can join, then whenever a new Stuart Woods title is added, staff place a club hold that hits every patron enrolled. Right now, if I take three different patrons from three different branches and add them to a single club, I will be forced to select a single pickup location which may be inaccessible to some or all of the patrons. To set three different pickup locations, I would need to place three different club holds for three different clubs. That has potential to get very messy, very quickly. Each branch would need a club for each author, which then makes it easy to enroll patrons in the wrong club and get their holds sent to the wrong branch. Ideally, all three patrons should be able to join a single club and get their holds sent to their respective home branches for pick up. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 24612] New: expirationdate blank if patron has more than one item from bib on hold
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24612 Bug ID: 24612 Summary: expirationdate blank if patron has more than one item from bib on hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It is impossible to print the expiration date on a hold slip (HOLD_SLIP) if the patron has more than one hold on that bib. The expirationdate comes back blank. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 25864] New: Case sensitivity breaks searching of some fields in ES5
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25864 Bug ID: 25864 Summary: Case sensitivity breaks searching of some fields in ES5 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com In Elasticsearch.pm: 1161 # Force lower case on indexed field names for case insensitive 1162 # field name searches 1163 lc($search_field->name), But in QueryBuilder.pm 1172 push @search_fields, [ 1173 $search_field->name, Now that we pass 'fields' for all generic searches this breaks things in ES5 To recreate: 1 - Have Koha using ES5 and Elasticsearch as search engine 2 - Enable DumpTemplateVarsIntranet and DumpSearchQueryTemplate 3 - Do a search in authorities using 'Search entire record' (abduction if using sample db) 4 - Note no results 5 - View the page source and find 'search_query' 6 - Note the uppercased fields 7 - curl 'es:9200/koha_kohadev_authorities/data/417?pretty' 8 - Note all fields lower-cased -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 22868] New: Separate Permissions for "Manage Purchase Suggestions" and "Enter Purchase Suggestions"
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22868 Bug ID: 22868 Summary: Separate Permissions for "Manage Purchase Suggestions" and "Enter Purchase Suggestions" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- It would be handy if we could have separate permissions for "Manage Purchase Suggestions" and "Enter Purchase Suggestions" After bug 11911 was pushed, it is now obvious to people who have the "Manage Purchase Suggestions" permission that they can go in and edit any. It would be great if we could separate it out and let staff only add purchase suggestions. Many of our branches have staff enter in any purchase suggestions on the staff side using the "Purchase Suggestions" tab when checking out a patron, but don't want them to have the ability to go manage other ones. 12219 Can help some with that by limiting to branch, but if we could also have the ability to only add and not manage, that would be helpful here. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 25526] New: Using Write Off Selected will not allow for a different dollar amount to be written off
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '20

24 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25526 Bug ID: 25526 Summary: Using Write Off Selected will not allow for a different dollar amount to be written off Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Using the Write Off Selected option in the Accounting Module, a user can not choose to write off a specific amount. If a user chooses to Write Off under the Actions button, then a specific amount can be written off as opposed to the full line item's amount. However, if the "Write Off Selected" is chosen a specific amount can not be typed in, Koha gives an error. 1. Have a fine on a Patron's account. 2. Choose the "Write off Selected" button 3. Enter an amount less than the amount owed by the patron. 4. Koha will give a yellow box with a note "You must collect a value greater than or equal to 2.00." The $2.00 is the amount that is attempted to write off (the amount less than the amount owed). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30