[Koha-bugs] [Bug 8506] return date of lost items recorded wrong

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8506

Barton Chittenden <barton at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |barton at bywatersolutions.com
           Severity|normal                      |major

--- Comment #1 from Barton Chittenden <barton at bywatersolutions.com> ---
This should be escalated, because it causes an inconsistency between
issues.date_due and items.onloan... this is one of the avenues for items to
show up as both "Checked out" and "Available" at the same time.

I've marked this as "Major".

This may also be linked to Bug 12363 (Marking an item as lost in koha always
returns it, but longoverdue.pl may no)

To replicate:

1) Check out an item.
2) Change the following dates in the database, so that the item will trigger as
long overdue:
-- items.onloan
-- issues.date_due
The following fields should probably also be back-dated, for the sake of
consistency with koha:
-- items.datelastseen
-- items.datelastborrowed
-- items.timestamp
-- issues.timestamp
-- issues.issuedate
3) Run longoverdue.pl
4) Navigate to the item in moredetail.pl. Change the lost status from
'Longoverdue (Lost)' to blank.
5) Navigate back to detail.pl, and note that the item now shows as both
'Available' and 'Checked out to <patron> : due <due date>'

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.