Bug 13266 - renewing an item doesn't remove lost
Summary: renewing an item doesn't remove lost
Status: RESOLVED DUPLICATE of bug 9805
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-17 15:04 UTC by Nicole C. Engard
Modified: 2015-03-18 16:21 UTC (History)
3 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 2014-11-17 15:04:40 UTC
When an item is renewed the lost status isn't removed - but if you check in a lost item it is.  It seems like the lost status should be removed when an item is renewed.

This is from IRC:
--------------

[08:26]  <nengard> hey #koha I'm wondering did renewing an item ever clear the lost status on that item? I don't think it did - but want to check before I report a bug/enh
[08:28]  <oleonard> nengard: Do you think it should or shouldn't?
[08:31]  <oleonard> If the item is long overdue (lost) I would say it should--if you renew it it's not overdue anymore!
[08:31]  <oleonard> ...but it doesn't in master.
[08:35]  <oleonard> ...and didn't in 3.14.x.
[08:37]  <nengard> i don't know really if it should or shouldn't
[08:37]  <nengard> when you check in an item that was lost it makes it not lost
[08:37]  <nengard> so i think renewing should be the same ... right?
[08:39]  <oleonard> I would consider it a bug, but it's a long-standing behavior so I wonder what others think.
[08:45]  <oleonard> In my library the only time someone would have something checked out which was lost would be long overdue (lost), and normally those items would not be eligible for renewal
[08:45]  <oleonard> So maybe it's just never come up for us.
Comment 1 Kyle M Hall 2015-03-18 16:21:56 UTC

*** This bug has been marked as a duplicate of bug 9805 ***