Web Client: Check In - "Route To" Field Sometimes Incorrect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Fix Released
|
Medium
|
Unassigned | ||
3.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Web Client - Evergreen 3.0.8
When an item is checked in from delivery and needs to go to a different library, the "Route to" column on the Check In screen shows the current library instead of its destination. If the item is checked in again, the correct information is displayed, as seen in the attached screenshot.
This only seems to happen if the item is in transit upon check in and is then sent in transit somewhere else.
This behavior is very similar to bug #1740537 but was not fixed by its patch.
I am able to replicate this issue every time with the following steps:
1. Sign in as Library A.
2. Check in an item owned by Library B that does not have any holds associated with it. This will send the item in transit to its home, Library B.
3. Place a hold on the item to be picked up at Library C.
4. Sign in as Library B.
5. Check in the item. [Upon check in, the item should show a "Route To" of Library C, but instead...] the column shows that the item needs to be transited to Library B instead of Library C.
Changed in evergreen: | |
milestone: | none → 3.5-alpha |
assignee: | nobody → John Amundson (jamundson) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
We are also finding this is true for items "coming home". If an item is owned by Library A and is in transit to and checked in by Library A, the Route To field will display Library A on the first scan and then the item's shelving location on the second scan. See attached image.