October 2018 - Koha-bugs - lists.koha-community.org

[Bug 15758] New: Move the C4::Branch related code to Koha::Libraries - part 4
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '21

23 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15758 Bug ID: 15758 Summary: Move the C4::Branch related code to Koha::Libraries - part 4 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 15629 Blocks: 15293 This fourth and last part will remove: - GetBranchName - GetBranchesLoop - GetBranches - GetBranch will move mybranch and onlymine to C4::Context and finally remove all occurrences of C4::Branch. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15293 [Bug 15293] Move the C4::Branch related code to Koha::Libraries https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15629 [Bug 15629] Move the C4::Branch related code to Koha::Libraries - part 3 -- You are receiving this mail because: You are watching all bug changes.

1 169

[Bug 20460] New: Staff can only change password through the change password button if patron hits failedloginattempts
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '21

23 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20460 Bug ID: 20460 Summary: Staff can only change password through the change password button if patron hits failedloginattempts Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If you use the system preference FailedLoginAttempts and a patron becomes blocked after reaching x failed login attempts, the user is prompted to reset their password. The system preference for OPACresetpassword must be turned on to allow patron to reset their password. If a patron experiences an issue resetting their password and needs staff intervention, it would be helpful to make staff aware that the account has been locked due to too many failed attempts on the patron’s detail page. Staff can click the change password button on circulation.pl or moremember.pl to reset the password. However, if staff click the edit button on circulation.pl or moremember.pl to reset the password, it does not change the password for the patron. It would be helpful to prompt staff to use the Change Password link in the staff UI and/or have the ability to update the password from the edit menu. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 21498] New: Possibility to renew early when automatic renewals are enabled
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '21

22 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21498 Bug ID: 21498 Summary: Possibility to renew early when automatic renewals are enabled Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: information(a)newcastle.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 80067 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=80067&action=ed… Patron checkouts screen - item scheduled for auto-renewal We're enabling automatic renewals for most of our borrowable items. We've noticed that when auto-renewal is enabled there isn't an option to renew early (before the date set for the automatic renewal to run), as shown in the screenshot attached. We think this might become a problem with some of our library members. Could something like a "renew now" button that would work alongside the automatic renewal be considered? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 20718] New: Add ability to have lists that are available to all list editors
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '21

17 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20718 Bug ID: 20718 Summary: Add ability to have lists that are available to all list editors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some librarians would like to have lists that can be shared among staff that have the lists permission. Test Plan: 1) Apply this patch 2) Create some private, public and 'staff' lists 3) Note only staff that can edit lists have access to the 'staff' lists -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 18968] New: API for online payments using GoPay gateway (Czech only)
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '21

17 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18968 Bug ID: 18968 Summary: API for online payments using GoPay gateway (Czech only) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rbit(a)rbit.cz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Online payments in the Czech Rep. can be paid using GoPay service. Documentation can be found at: https://help.gopay.com/cs/tema/integrace-platebni-brany/technicky-popis-int… We plan to use it in external systems like VuFind. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 20815] New: Development FY18 New System Preference
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '21

16 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20815 Bug ID: 20815 Summary: Development FY18 New System Preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1 - Add a enw system preference "Don'tForgiveLostAfter" which would allow specification of a range of time 2 - modify the check in routine to check the value of the itemlost_on field and only refund if before this time 3 - Add feedback for circulation staff to alert that item was lost but fee is not refunded -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 19266] New: Add ability to match on 001 or 005 during import of records
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '21

15 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19266 Bug ID: 19266 Summary: Add ability to match on 001 or 005 during import of records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 16181] New: Limit number of tags loaded initially for tag cloud
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16181 Bug ID: 16181 Summary: Limit number of tags loaded initially for tag cloud Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a patron has an large number of tags (say 3,421) the tag cloud takes an inordinately long time to load. Maybe we could enforce a limit on initial load and then allow user to load more or paginate through all? -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 16785] New: Autocomplete broken on overdues report
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '21

08 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16785 Bug ID: 16785 Summary: Autocomplete broken on overdues report Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/circ/overdue.pl OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, koha-bugs(a)lists.koha-community.org, kyle.m.hall(a)gmail.com If you have a patron attribute defined which is searchable and linked to an authorized value, that attribute will show up in the overdue report filter form as an autocomplete field. The autocomplete is broken for cases where more than one result is returned by the search. -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug.

1 20

[Bug 20662] New: The "most poplular" function on the opac does not honour opac supression
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '21

02 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20662 Bug ID: 20662 Summary: The "most poplular" function on the opac does not honour opac supression Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The "most popular" function on the OPAC does not honour the opac suppression in the 942$n subfield. I think this is because "most popular" is based on a database query, and the opac suppression is in a MARC field which is indexed in Zebra. I think the solution is probably to create a biblio.suppressed field and have the 942$n store data in that field. Then we check that database field for things like "most popular" and other database queries. -- You are receiving this mail because: You are watching all bug changes.

1 6