Bug 11151 - hold error message wrong if in transit
Summary: hold error message wrong if in transit
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-28 18:43 UTC by Nicole C. Engard
Modified: 2023-09-23 20:56 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:
Circulation function:


Attachments
error (77.71 KB, image/png)
2013-10-28 18:43 UTC, Nicole C. Engard
Details
item in transit - not waiting (49.18 KB, image/png)
2013-10-28 18:43 UTC, Nicole C. Engard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2013-10-28 18:43:35 UTC
Created attachment 22475 [details]
error

If you try to check out and item that is in transit to another branch to fill a hold the error message says:


"Item 1001 ways to be romantic : (0114972293947) has been waiting for Lloyd Bonafide (1114911111119) at South Holiday since
Cancel hold
Revert waiting status"


But the item is in transit - not waiting - I don't know what will happen if I ignore this because I'm in training right now, but I wanted a record of the fact that error message reads wrong - and probably will cause problems with transfers.  See attached images.
Comment 1 Nicole C. Engard 2013-10-28 18:43:54 UTC
Created attachment 22476 [details]
item in transit - not waiting
Comment 2 Nicole C. Engard 2015-04-20 15:22:37 UTC
Has anyone seen this in master? This is an old report.
Comment 3 Owen Leonard 2016-08-09 18:29:41 UTC
I can reproduce this in master. The error message still reads the same. However, I can't see that anything is going wrong with transfers. If you revert the waiting status to check out the transfer is marked as completed. So I think the full extent of this bug is the text problem.
Comment 4 Emily Lamancusa (emlam) 2023-09-23 20:56:23 UTC
Is this still valid?