September 2021 - Koha-bugs - lists.koha-community.org

[Bug 23819] New: Allow status to be set during creation of a purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23819 Bug ID: 23819 Summary: Allow status to be set during creation of a purchase suggestion 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 Here is the workflow where this would be helpful: 1. Patron asks if we have a book. 2. Staff member checks in catalog that we don't have it, offers to make purchase suggestion. 3. Staff members fills out purchase suggestion and currently: Saves the suggestion and has to edit again to be able to edit status to "Sent to Adult Librarian" Would be nice if they could instead set that status on creation to reduce clicks. In this case 3 would say: 3. Staff member fills out purchase suggestion and sets status to "Sent to Adult Librarian" then saves purchase suggestion. Lisette -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24454] New: currency formatting from JS
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24454 Bug ID: 24454 Summary: currency formatting from JS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com API calls in OPAC brings raw JSON. We need a way to format data into the configured currency from JS. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 29097] New: Overdue fines for lost items reinstated even when item returned on Fine Free mode
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29097 Bug ID: 29097 Summary: Overdue fines for lost items reinstated even when item returned on Fine Free mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 23091 To recreate: - Set WhenLostChargeReplacementFee ON, WhenLostForgiveFine ON - Set you refund lost item value to EITHER refund lost fee and charge a new overdue fine OR refund lost fee and restore overdue fine - check an item out with a due date in the past, run the fines cron - mark the item lost, confirm the overdue fine is forgiven and a lost fee is applied - set checkin to Fine Free mode and check the item in - confirm your lost fee is gone and your overdue is back If the item is checked in on Fine Free mode, the fine should not come back. Or at least that should be a configurable option via a syspref. We have libraries set Fine Free on for all checkouts for amnesty periods. This sort of return of long-lost items is exactly what they're trying to incentivize with such a program. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 [Bug 23091] Add options to charge new or restore forgiven overdues when a lost item is returned -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 29096] New: Removing a lost status via item edit refunds lost fee without reinstating overdue fine
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29096 Bug ID: 29096 Summary: Removing a lost status via item edit refunds lost fee without reinstating overdue fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 23091 To recreate: - Set WhenLostChargeReplacementFee ON, WhenLostForgiveFine ON - Set you refund lost item value to EITHER refund lost fee and charge a new overdue fine OR refund lost fee and restore overdue fine - check an item out with a due date in the past, run the fines cron - mark the item lost, confirm the overdue fine is forgiven and a lost fee is applied - edit the item to remove the lost status - confirm the lost status is refunded but the overdue fine hasn't returned We're removing the lost fee on the assumption that we've found the item and therefore the patron doesn't owe us the replacement anymore. That assumption should also result in restoring/re-charging the overdue fine. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 [Bug 23091] Add options to charge new or restore forgiven overdues when a lost item is returned -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 17996] New: longoverdue.pl should not set 'datereturned' when --mark-returned option is used.
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '21

23 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17996 Bug ID: 17996 Summary: longoverdue.pl should not set 'datereturned' when --mark-returned option is used. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When longoverdue.pl returns items, it sets old_issues.returndate to the current date. This means that when staff look at the borrowers' circulation history, they see a returndate displayed, which is confusing. We don't lose information by not setting old_issues.returndate, because items.itemlost_on will contain the date that the item was lost. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 29088] New: Warning when connection to memcached fails is too long
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '21

22 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29088 Bug ID: 29088 Summary: Warning when connection to memcached fails is too long Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Actually when connection to memcached fails a warning is created : unless ($ismemcached) { warn "\nConnection to the memcached servers '@servers' failed. Are the unix socket permissions set properly? Is the host reachable?\nIf you ignore this warning, you will face performance issues\n"; return $self; } This will generate 2 lines plus one empty line. It it shown even for CLI scripts. During some system operations or bash scripts, we may shutdown memcached on purpose. In this case warning is annoying. I propose we show a sorter text, and maybe a link to a wiki page. We may choose to remove this warning for it can SPAM log files. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 28684] New: Superfluous -or condition in few article request queries
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '21

22 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28684 Bug ID: 28684 Summary: Superfluous -or condition in few article request queries 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org - -or => [ - status => Koha::ArticleRequest::Status::Pending, - status => Koha::ArticleRequest::Status::Processing - ] + Koha::ArticleRequest::Status::Pending, + Koha::ArticleRequest::Status::Processing, -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 29081] New: Lost item behavior can result in duplicate fines
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '21

22 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29081 Bug ID: 29081 Summary: Lost item behavior can result in duplicate fines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 23091 If one's lost item refund behavior is set to charge a new when a lost item is found, but one has WhenLostForgiveFine turned off, then the patron ends up with 2 identical fines. The original overdue never goes away, and a new one is created anyway. I'd like to just block creation of the second fine. If that's not feasible, we should at least put a warning on the refund area in circ rules. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 [Bug 23091] Add options to charge new or restore forgiven overdues when a lost item is returned -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29080] New: Missing data trail for reduced fine
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '21

22 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29080 Bug ID: 29080 Summary: Missing data trail for reduced fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 23091 To recreate: - Set MarkLostItemsAsReturned to ON for all cases, WhenLostChargeReplacementFee ON, WhenLostForgiveFine ON - Set you refund lost item value to refund lost fee and charge a new overdue fine - set a circ rule to charge $1 per day overdues - check out an item, setting its due date to 7 days ago - run the fines cron, see your $7 accruing fine - mark the item lost, confirm the $7 fine is forgiven - check the item in, backdating the checkin to 5 days ago - confirm your new fine is $2, but old_issues.returndate still shows the time at which this item was marked lost In this situation, I can't find anything in the data to explain why the fine is $2. That's the correct amount, given the actions, but if one stumbled on this patron after the fact one would have a hard time figuring out what happened. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 [Bug 23091] Add options to charge new or restore forgiven overdues when a lost item is returned -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 10919] Use the date of closing basketgroup for calculating late orders
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '21

22 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10919 --- Comment #2 from mathieu saby <mathsabypro(a)gmail.com> --- This bug was still assigned to me. Of course it is no more the case since 2013 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0