Summary: | Any lost value triggers refund message on check in, even if it doesn't apply | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrew, clackman, gmcharlt, kyle.m.hall |
Version: | 19.11 | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Christopher Brannon
2020-07-01 22:12:07 UTC
I think I filed a similar bug to this sometime. The negative/positive would be hard to implement nicely at this point in time without giving some grief to libraries (lots of changes required in a lot of libraries as the default 'missing' is positive). So I'd vote for the second option. Could it also be an alternative to not show the message if the item is no longer checked out? It seems like we've got two separate things here. First, there's a bug with the existing functionality, that it's not being accurate about whether or not a fee will be refunded. Looks like that's covered in bug 11723. Second, there's an enhancement to introduce functionality for some lost values to not generate refunds. Let's maybe made this bug focus on that? Maybe we add a corollary syspref to RefundLostOnReturnControl that takes a list of exceptions? Or just change RefundLostOnReturnControl so instead of a yes/no switch one enters a list of lost status for which one wants to refund? And leave blank if no refund is desired? I down with the second idea. Just have a list in place of the control. If there is nothing there, nothing happens. We only list what we want action on. Wish I could edit my comments in bugzilla sometimes. :/ It looks like the bug description should be updated? |