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

[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 24604] New: Add 'Pay' button under Transactions tab in patron accounting
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '20

10 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24604 Bug ID: 24604 Summary: Add 'Pay' button under Transactions tab in patron accounting Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 17

[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 24538] New: REMOTE_USER set to undef if koha_trusted_proxies contains invalid value
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '20

08 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24538 Bug ID: 24538 Summary: REMOTE_USER set to undef if koha_trusted_proxies contains invalid value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If koha_trusted_proxies contains an invalid or unparseable value, say due to a typo, like "1.1.1.", it'll treat it as a 0.0.0.0/0 mask and match against everything. In my tests, this leads to REMOTE_USER being set to undef. (On the plus side, at least a 0.0.0.0/0 mask leads to zero privileges rather than all privileges.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 22823] New: Koha::Library needs a method for obtaining the incoming email address
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '20

07 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22823 Bug ID: 22823 Summary: Koha::Library needs a method for obtaining the incoming email address 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- There's a code pattern emerging (in bug 5770 and bug 22821 at least to my knowledge) where we grab a branches email address to send notifications to the branch. However, it's prone to make mistakes in the fallback order for assigning that address so we should factor it out into a method that can be called from Koha::Library. Should be as simple as >sub to_email { > my $self = shift; > return $self->branchreplyto || $self->branchemail || C4::Context->preference('ReplytoDefault') || C4::Context->preference('KohaAdminEmailAddress'); >} along with some appropriate POD and a walk of the codebase to replace existing occurrences of the pattern. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[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