Bug 4809 - Allow to pay lost item replacement fee when changing the lost status
Summary: Allow to pay lost item replacement fee when changing the lost status
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks: 14825
  Show dependency treegraph
 
Reported: 2010-05-24 20:39 UTC by Nicole C. Engard
Modified: 2024-01-19 11:51 UTC (History)
7 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2010-05-24 20:39:34 UTC
marking item 'lost and paid for' doesn't put the item link on the fines listing and it shows the amount as 0 instead of the fee that was paid and marking it paid - this means there is no record of the money changing hands
Comment 1 Owen Leonard 2010-06-24 18:35:35 UTC
It appears to me that if you mark a checked-out item as "lost and paid for" that nothing happens other than the status getting set. The item remains checked out and there is no entry under the patron's account listing--I don't see even a zero amount.

I'm assuming that these steps should occur:

1. The item should be checked in (bypassing any pending hold requests)
2. The item should be marked as "lost and paid for."
3. An entry should be added to the patron's list of fines for that item
4. An entry should be added to the patron's list of fines showing the item paid for.
Comment 2 Nicole C. Engard 2010-06-24 19:05:43 UTC
You are correct - recent patches seemed to have made changes that removed even the zero line from the account listing - it was there when I reported the bug but I tested again today and it is not there.
Comment 3 Nicole C. Engard 2011-11-07 16:36:13 UTC
I believe this is still an issue in 3.6
Comment 4 Nicole C. Engard 2012-09-25 12:02:46 UTC
This is still an issue in 3.8.x
Comment 5 Chris Cormack 2013-10-21 17:00:34 UTC
In master, if I mark it lost and paid for, I get the charge added, and it is checked in

However it is not marking the charge paid for.

Testing with other syspref settings now.

So from owens list

1, 2, and 3 are working. It is just 4 (the item being paid for) that is not yet working
Comment 6 Chris Cormack 2013-10-21 17:09:43 UTC
I see why this isn't working, the lost values are totally editable (Authorised Values) so all values of Lost get treated the same.

If we made it be a magic number, we would then have to make it no longer editable. I don't think we can safely do this with the drop down. I think we would have to add a checkbox. Mark it lost, and choose the paid for checkbox.

Then it wouldn't break whenever anyone changed the authorised values.

How does that sound?
Comment 7 Amber Hunt 2013-10-21 17:57:45 UTC
I think what Chris describes will work well. It would also mean that it would be easy to mark something previously marked lost as paid.
Comment 8 Martin Renvoize 2019-05-24 14:04:19 UTC
Is this still actually the case.. feels like we may be able to close this at this point.
Comment 9 Katrin Fischer 2019-11-03 21:29:06 UTC
I think the comment from Chris on comment#6 is still valid.

There is no special behavior tied to any of the lost values - they all do the same thing. If we want a way to immediately mark 'paid' when changing the lost status, this will need more work.

Another way might be a pref, where you list the lost values that you want to do that for.