March 2019 - Koha-bugs - lists.koha-community.org

[Bug 21292] New: Patron Deletion Tool
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '20

20 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21292 Bug ID: 21292 Summary: Patron Deletion Tool Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 78312 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=78312&action=ed… this is what Koha produces from a patron list of 3 people when only 1 could be deleted. Currently, the patron deletion tool will not delete patrons who has fines and/or checkouts. Unfortunately, the tool does not indicate the patrons that were not deleted because of these constraints. It would be nice to have Koha identify the # of patrons that were requested to be deleted, the number of patrons successfully deleted (with possibly a list) and the number and specifics of the patrons that could not be deleted due to checkouts/fines. This would give clear indication what was accomplished with this tool for libraries. The current functionality of entering patrons that have checkouts/fines that have been requested to be deleted, Koha all but ignores those patrons and doesn't say anything. For example, if I had a patron list of 3 patrons and I requested Koha delete this entire list of patrons. If 2 of those patrons had fines/checkouts, Koha would only display 1 patron deleted. This would not be a link to the patron that was deleted - just a simple number. In addition, the manual does not have correct information regarding this tool - as it indicates - this is quoted from the 17.11 manual : "Important Patrons with outstanding fines or items checked out are not saved. They are not completely removed from the system (they are only moved to the delete_borrowers table), but this tool does not provide as many checks as one may desire." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 19426] New: Single Branch Exception to a Repeating Holiday Affects Closed Branches
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '20

17 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19426 Bug ID: 19426 Summary: Single Branch Exception to a Repeating Holiday Affects Closed Branches Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: cslone(a)camdencountylibrary.org QA Contact: testopia(a)bugs.koha-community.org Scenario: You have some branches that are open every day of the week, and several that are closed on Sundays all year round. Due to the fact that these Sunday closures do not affect every location, each branch that is closed on Sundays has its own repeating holiday set up. However, if you add an exception for a single branch to this holiday it will affect the due dates for the items being checked out from any of the other branches that are still closed that day. This is despite the fact that the calendar for the closed branches still lists them as being closed. To test: 1.) Set the "useDaysMode" preference to "calculate the due date using the calendar to push the due date to the next open day." 2.) Create a repeating holiday (individually) for two or more branches. 3.) Add an exception to this repeating holiday for one of the branches. 4.) Confirm that the exception is shown only for the intended branch. 5.) Log-in to the branch to which you did not add the calendar exception and checkout an item that should get pushed forward to be due the day after the repeating holiday - For example, you have the repeating holidays on Sunday, are logged-in on a Thursday, and checkout an item that circulates for three days, which should then get pushed from being due on Sunday to Monday 6.) Confirm that the item was made to be due on the repeating holiday for that branch instead of the day after -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 21063] New: Allow columns in intranet ILL request datatable to be customisable
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '20

15 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21063 Bug ID: 21063 Summary: Allow columns in intranet ILL request datatable to be customisable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Currently the columns in this datatable are static, they should be customisable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 93

[Bug 20563] New: ILL request list gives no indication of source and/or target
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '20

15 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20563 Bug ID: 20563 Summary: ILL request list gives no indication of source and/or target Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Currently when viewing a list of ILL requests in staff view there is no indication of with whom the request was placed. What will be displayed here will depend upon the backend on which the request was placed. For example, with BLDSS the displayed string will simply be BLDSS, whereas with FreeForm some indication of the partner library would be required. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 20571] New: Rancor - Keybinding configuration per users
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '20

11 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20571 Bug ID: 20571 Summary: Rancor - Keybinding configuration per users 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 18904 With bug 18904 there is the feeling that we should provide a way to let the users define their own keybinding. It could be system-wise in a first time (syspref) and then per user Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18904 [Bug 18904] Advanced editor - Rancor - Add authority support -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 19026] New: System Preferences that include a list of fields is not displayed correctly in Chrome
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '20

11 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19026 Bug ID: 19026 Summary: System Preferences that include a list of fields is not displayed correctly in Chrome Change sponsored?: --- Product: Koha Version: 16.11 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 65430 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65430&action=ed… This is how it is displayed in Chrome. Currently in the latest version of Chrome: 60.0.3112.78 the system preference OPACSuggestionMandatoryFields does not show the list of fields in the display. This is also the case in these system preferences : OPACadvsearchmoreoptions, Opacadvsearchoptions, opacexportoptions- there may be more. >From the browser of Firefox, they display correctly. Included screen shots of this behavior. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 17734] New: Make possible to pay and writeoff from boraccount page and make action buttons split button
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '20

10 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17734 Bug ID: 17734 Summary: Make possible to pay and writeoff from boraccount page and make action buttons split button Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 21373] New: Checkout not possible when biblio level hold but other items could satisfy it
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '20

09 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21373 Bug ID: 21373 Summary: Checkout not possible when biblio level hold but other items could satisfy it Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assume following 1. There is bib record with 5 items available 2. Patron A makes a bib level hold for the record Now we try to checkout one item from the bib record for patron B Result: I get a warning menu saying that this item is on hold Expected result: I can proceed with the checkout and no warnings come unless there are no available items, i.e., biblio level hold number <= items available. I refactored the C4/Circulation.pm a bit so that we can use the code from CanBookBeRenewd function to make the checkout work the same way as it is possible with renewals, i.e. renewals are possible even if there is a biblio level hold and some other available item that can satisfy the loan. I will send this patch ASAP. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22296] New: Invoice adjustments are not populating to budget views
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '20

06 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22296 Bug ID: 22296 Summary: Invoice adjustments are not populating to budget views Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When invoice adjustments were added they were made to populate spent.pl and ordered.pl, however, they are not taken into account on aqui-home.pl or aqbudgets.pl They must be added in to GetBudgetHierarchy -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 18314] New: Account lockout
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '20

06 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18314 Bug ID: 18314 Summary: Account lockout Change sponsored?: Sponsored Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To prevent brute force attacks on Koha accounts, staff and opac, we need to implement an account lockout process to Koha. After a number of failed login attempts a users account would become locked. The user would then need to use the reset password functionality to send a reset token to their email account. After a successful password reset the lockout flag would be removed. The number of failed login attempts before lockout will be configurable using a system preference. -- You are receiving this mail because: You are watching all bug changes.

1 60