When Aborting a Transit, items should not automatically get a status change.
Bug #1306666 reported by
Michele Morgan
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Low
|
Unassigned | ||
2.9 |
Fix Released
|
Low
|
Unassigned |
Bug Description
When a staff user aborts a transit on an item, the item's status is updated as follows:
set to Reshelving, if it's a hold transit
set to the last status prior to the transit if it's a home transit.
There can, for various reasons, be "hanging transits" on an item that did not get closed out properly. These can hang around for some time. Aborting these hanging transits will apply an inappropriate status change to items that are not currently in transit.
This can potentially break active circulations and cause confusion due to inexplicable item status changes.
tags: | added: wishlist |
Changed in evergreen: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
milestone: | 2.10.1 → 2.10.2 |
Changed in evergreen: | |
milestone: | 2.10.2 → 2.10.3 |
Changed in evergreen: | |
milestone: | 2.10.3 → 2.10.4 |
Changed in evergreen: | |
milestone: | 2.10.4 → 2.10.5 |
Changed in evergreen: | |
milestone: | 2.10.5 → 2.10.6 |
no longer affects: | evergreen/2.8 |
no longer affects: | evergreen/2.7 |
summary: |
- When Aborting a Transit, items should automatically get a status change. + When Aborting a Transit, items should not automatically get a status + change. |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This has been a long standing (though minor) annoyance for me as well. Making sure new transit slips are appropriately generated will be critical for front line staff as well.
I would think we would want it to behave appropriate per floating collections rules as well. If it's transited between two locations that share a floating collection I don't want it sent back unnecessarily.