Comment 3 for bug 2053255

We've also encountered this recently on 3.11.3. If an item is in transit for a hold and ends up being checked in at a library other than its destination, Evergreen only considers the fact that the item should still be in transit to its destination and doesn't bother to check whether it is still needed to fulfill the hold at its end destination.

We ended up with a very weird variation of this that interacted with another bug described in 2058786.