Item states (status)
(UXPROD-1321)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Item states (status) |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Emma Boettcher | Assignee: | Thomas Trutt |
| 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: | None | ||||||||||||||||||||||||||||||||||||
| PO Rank: | 79 | ||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R3 | ||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem:
Closing orders and receiving items does not affect the item status of items with any other statuses besides the ones listed above. In scope
Out of scope
Use case(s)
Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Jacquie Samples [ 30/Sep/20 ] |
|
If we are talking about adding a local item process (aka item status), and not adding a new type of item state, then we do agree that this functionality should be developed. However, this should not be contained to just orders and receiving. This is cross-app functionality, not one that is only applicable to the Orders and Receiving Apps. We (Duke Metadata Team) are not ranking this Jira today since we prefer that time be spent on creating the 3-part item state over customizing the current model's item status. |
| Comment by Kristin Martin [ 23/Oct/20 ] |
|
From Chicago: At this point, we are not planning to use custom item statuses for real items that will be ordered or received and will initially limit our use of custom item status to DUMMY items (like for analytics or other items where we have an intellectual representation but not a true item). So I don't think we'll initially be using custom item status in the acquisitions workflow, but I might be missing a use case. |