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: |
|
||||||||||||||||||||||||||||||||||||||||
| Release: | Not Scheduled | ||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Item states (status) | ||||||||||||||||||||||||||||||||||||||||
| Development Team: | None | ||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: This feature is meant to encompass needed work in the Bulk Edit area. 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 this Jira is describing about adding a local item process (aka item status), and not adding a new part to the 3-part item state model, then we do agree that this functionality should be developed. This is cross-app functionality, not one that is only applicable to specific 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 ] |
|
If we are able to get the DUMMY/INTELLECTUAL item status to represent a non-real item (like an analytic or bound-with), then we will not need custom item state at Go-Live. |