Item states (status)
(UXPROD-1321)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Item states (status) |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Erin Nettifee | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Epic Link: | Item states (status) | ||||||||||||||||
| Development Team: | Vega | ||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||
| Description |
|
Current situation or problem: Currently, an item that has a status of "Order closed" can still be requested. This is not desired behavior, because if the order was closed, the item was not received and the order itself is no longer being processed. Accordingly, we need to change current request whitelist behavior so that if the item status is *Order closed*, holds, pages and recalls are all not allowed. In scope
Out of scope
Use case(s) Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Erin Nettifee [ 20/Oct/22 ] |
|
Stephanie Buck Tim Auger I'm doing some cleanup on old item state tickets that were managed by Emma Boettcher. This is split from a larger placeholder ticket and has a front-end and back-end component, but I think should be pretty straightforward work. I've attached the UI story that Emma wrote (
|