Item states (status)
(UXPROD-1321)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Item states (status) |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Emma Boettcher | Assignee: | Ryan Taylor |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | epam-folijet, inventory, permissions | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Release: | Not Scheduled | ||||||||||||||||||||||||||||||||
| Epic Link: | Item states (status) | ||||||||||||||||||||||||||||||||
| Development Team: | Folijet | ||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 1 | ||||||||||||||||||||||||||||||||
| PO Rank: | 67 | ||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R3 | ||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||||||||||||||||||||||||||
| Description |
|
FOLIO allows some item status changes to take place on the item record (as opposed to processes in other apps). This feature creates separate permissions for changing item status based on what the user is changing the item status from. Restrictions on changing item status from item record (regardless of permissions):
|
| Comments |
| Comment by Jacquie Samples [ 23/Sep/20 ] |
|
This is been documenting too narrowly. We need more flexibility and granularity with permissions. Due to the lack of Workflow Engine development, human errors will creep in and need to be cleared by batch processing, as it is done now. This means that permissions for batch changing Item states (and other item data) needs to available to only some staff roles. Additionally, some super-users Should be able to make manual changes at the item level because not all item change needs are for RA and RM use cases. |
| Comment by Karen Newbery [ 24/Sep/20 ] |
|
Not written comprehensive enough; Should include item statuses 'to' not just 'from' Should prevent invalid status changes such as from lost to long lost or lost to suppressed. Should be able override with certain permissions. Wouldn't need this if we had the workflow engine. |
| Comment by Kristin Martin [ 23/Oct/20 ] |
|
From Chicago: In Inventory there are very few item statuses that we need to set: Missing/ Lost (based on workflow) or Withdrawn. Other statuses such as intellectual / dummy item will be set at item creation so I do not think is a permission issue |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Dec/23 ] |
|
Moved from Prokopovych backlog to Folijet Backlog cc: Ryan Taylor |