Bug 13595 - Checking out an issued item doesn't return it after confirmation
Summary: Checking out an issued item doesn't return it after confirmation
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: 3.18
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-19 11:37 UTC by Josef Moravec
Modified: 2015-12-03 22:00 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 Josef Moravec 2015-01-19 11:37:34 UTC
When you are checking out an issued item, we can see this confirmation:

Item "Title (barcode)" is checked out to "Member (cardnumber)"
Check in and check out?

But after clicking "Yes" button, the item is just issued to current member, but is NOT checked in before!

It looks like the all confirmations works the same way, but this one is special and need additional action (checking in the item).
Comment 1 Owen Leonard 2015-01-20 13:35:25 UTC
(In reply to Josef Moravec from comment #0)
> But after clicking "Yes" button, the item is just issued to current member,
> but is NOT checked in before!

Are you saying that the item remains checked out to both patrons, or that some action which is supposed to be performed upon check-in is not being performed? 

When I test it in master it works as I expect it to: The item is removed from the previous patron's account and checked out to the current one.
Comment 2 Josef Moravec 2015-01-20 13:47:21 UTC
Yes, but now I tested it on master and on another 3.18.2 stable installation and everything went right, so It looks like there is something wrong with one concrete installation... I'll investigate it deeper...
Comment 3 Josef Moravec 2015-02-19 11:23:01 UTC
I can't reproduce it now, so closing this bug.