Bug 7635

Summary: ignoring hold still marks it in transit
Product: Koha Reporter: Nicole C. Engard <nengard>
Component: CirculationAssignee: Kyle M Hall <kyle.m.hall>
Status: CLOSED INVALID QA Contact:
Severity: critical    
Priority: P5 - low CC: ago, gmcharlt, liz
Version: 3.10   
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:
Attachments: example for checked out and waiting

Description Nicole C. Engard 2012-03-01 16:32:17 UTC
Steps reproduce:

1. checkin item
2. ignore hold prompt to transfer
3. item says in transit on holds tab
4. item not listed in transfers to receive
5. item not listed in transit on the holdings table on the detail screen

So the item isn't really in transit, but the holds tab seems to think it is and it's confusing to librarians looking at the holds tab.
Comment 1 Albert Oller 2012-08-31 13:43:20 UTC
The same thing is happening with checked-out items.  Hold still appears in holds queue, awaiting pick-up on the patron record, and both checked out and waiting on the item record.
Comment 2 Albert Oller 2012-08-31 13:43:58 UTC
Created attachment 11912 [details]
example for checked out and waiting
Comment 3 Kyle M Hall 2013-04-10 17:12:08 UTC
I cannot reproduce this on master or 3.10.x. Nicole, can you retest to confirm?

(In reply to comment #0)
> Steps reproduce:
> 
> 1. checkin item
> 2. ignore hold prompt to transfer
> 3. item says in transit on holds tab
> 4. item not listed in transfers to receive
> 5. item not listed in transit on the holdings table on the detail screen
> 
> So the item isn't really in transit, but the holds tab seems to think it is
> and it's confusing to librarians looking at the holds tab.
Comment 4 Liz Rea 2013-04-10 23:27:08 UTC
We'd probably also need to know what settings you have set in Staff Client -> Holds, as that might influence this behaviour.

Liz
Comment 5 Owen Leonard 2013-05-10 13:13:06 UTC
(In reply to comment #3)
> I cannot reproduce this on master or 3.10.x. Nicole, can you retest to
> confirm?

Me neither!
Comment 6 Owen Leonard 2014-07-10 17:34:02 UTC
No one seems to be able to reproduce this issue, and the report refers to a version which is no longer maintained. Closing as invalid.