After that change, when there is a movement from A to B in started state, Item_getCurrentSiteValue will consider that this movement has already reached B.
Before this change, Item_getCurrentSiteValue was returning None, which somehow makes sense because started movement is in transit state, so the item has left A but not yet reached B, so it is in an unknown location.
Low level current tracking list API ( getCurrentTrackingList ) does not return items for started movements.
Honestly, I do not know if this is by design. ( @all anybody knows ? )
I will work on adding missing tests, but please tell me if I am wrong in thinking it should return None.
@gabriel @rafael @tb @tc do you remember why this change was introduced ? Maybe that behaviour of returning None should be only at the level of Item_get* scripts ?