Item states (status) (UXPROD-1321)

[UXPROD-2567] Prioritizing "needed for" Created: 07/Jul/20  Updated: 12/Mar/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Item states (status)

Type: New Feature Priority: TBD
Reporter: Emma Boettcher Assignee: Charlotte Whitt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-1530 Implement Needed for in the Three-Par... Draft
Epic Link: Item states (status)
Development Team: None
PO Rank: 30
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R3
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R3

 Description   

When an item is needed for multiple staff processes, display those staff processes in the interface in a particular order, based on the order in which they should be fulfilled.

  • Include a default priority when configuring "needed for" values in item settings
  • If an item has multiple "needed for", display them in order of priority in Inventory and anywhere else needed for displays
  • Allow users to edit the priority of a "needed for" on an item record, so that it can display in a different order other than the default priority


 Comments   
Comment by Karen Newbery [ 24/Sep/20 ]

Duke MMIT- order needs to be institution specific and permissions at each level of CRUD. Wouldn't need this if we had the workflow engine.

Generated at Fri Feb 09 00:25:02 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.