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

[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

[Bug 18421] New: Make Coce cover images available for staff search
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '20

03 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18421 Bug ID: 18421 Summary: Make Coce cover images available for staff search 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: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When turned on, Coce cover images appear in the OPAC only, not staff interface. (Coce Cover images - settings in enhanced content.) Desired setting would be like Amazon cover settings - the ability to turn on Coce images for the OPAC and/or the staff interface separately. Coce server needs Koha searches to populate it with cover image links. While it is collecting them, images do not display on the first time search results. To make them display would need a refresh or a programmed time delay and re-query to the Coce server. This is not useful for public OPAC. While the Coce server is being populated with links it is desirable to have only the staff interface using Coce. After a time, when the Coce server has accumulated a large collection of links, it would then be turned on for public OPAC and used by both. I have Koha 3.22.07, and am testing with the Bywater Coce server. If this is under way or in more recent versions already, please comment. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 73

[Bug 18250] New: koha-common should start after memcached
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '20

03 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18250 Bug ID: 18250 Summary: koha-common should start after memcached Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 20897] New: Add generic cronjob to run plugins with a 'cronjob' method
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20897 Bug ID: 20897 Summary: Add generic cronjob to run plugins with a 'cronjob' method Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Sometimes there are ad-hoc cronjobs that need to be setup for a site, or there are plugins that need some regular tasks done. I was thinking an easy solution might be to package a generic cronjob into koha that would run daily (or whenever) to check for plugins with a cronjob method. The plugins could allow for configuration of the job in their configure method so that users could have control over some jobs. Could be used for emailing reports or other things that might benefit from a user facing solution. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 19508] New: When returning a lost item, Koha claim to have applied a refund when it has not
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '20

02 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19508 Bug ID: 19508 Summary: When returning a lost item, Koha claim to have applied a refund when it has not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com 1) Create a new item 2) Set it to 'missing' from the edit item screen (you might have to change the visibility setting of this subfield in order to do that) 3) Return the item 4) Verify that Koha reports: A refund has been applied to the borrowing patron's account. This message should only be shown, when an actual refund has been applied. It would also be nice to link to the patron in question in the message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 22167] New: Allow itemnumber column to be labelled differently when using bach item edit feature
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22167 Bug ID: 22167 Summary: Allow itemnumber column to be labelled differently when using bach item edit feature Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 19233 added a feature that allows you to send a list of items to the item batch edit from a saved SQL report. At the moment this only works, if your column is displayed as itemnumber. Example: Works: show itemnumber from items; Doesn't work: show itemnumber as "Item#" from items; This is not nice for translations. It would be nice if there was a different way to mark the itemnumber and explicitly activate the feature. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 22434] New: correct item callnumber search link
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22434 Bug ID: 22434 Summary: correct item callnumber search link Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Many places show item callnumber as a link to a search on this callnumber. The correct way is : (opac-)search.pl?q=callnum:%22[% callnumber | uri %]%22 I propose an include that creates think search link. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 20194] New: Display items.ccode as well as both biblioitems.itemtype and items.itype in circulation screens
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '20

29 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20194 Bug ID: 20194 Summary: Display items.ccode as well as both biblioitems.itemtype and items.itype in circulation screens 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: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment in circulation screens only one "item type" is displayed, biblioitems.itemtype or items.itype, depending on the item-level_itypes system preference. It is however possible for libraries to use both, biblioitems.itemtype to qualify the record, and items.itype to qualify the item itself. In such a scenario only one of the two will be displayed on the circulation screen. It is also possible for libraries to use items.ccode to further refine the description of their items, but this information is not displayed on circulation screens. This enhancement will make all this information more visible in circulation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 16528] New: Add ability to parallel process fines to fines.pl
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '20

29 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16528 Bug ID: 16528 Summary: Add ability to parallel process fines to fines.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On very large sites with thousands of overdue items, fines.pl may take an incredibly long time to complete. It may be possible to speed up fines.pl by allowing it to fork children that run in parallel. -- You are receiving this mail because: You are watching all bug changes.

1 10