Item states (status) (UXPROD-1321)

[UXPROD-2253] Item status cleanup: Order closed, In process Created: 06/Feb/20  Updated: 20/Oct/22  Resolved: 20/Oct/22

Status: Closed
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: Duplicate Votes: 0
Labels: round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-793 Order closed: check in Closed
is defined by CIRC-794 Backend: Order closed: check out Closed
is defined by CIRC-795 Backend: Order closed: prevent requests Closed
is defined by UIIN-978 Change item status to In process Closed
is defined by UIIN-1166 Permissions: mark item in process Closed
is defined by UIIN-988 Order closed: show in Inventory searc... Closed
Issue split
split to UXPROD-3862 Disallow requesting for items with st... Open
split to UXPROD-3863 Warn and require confirmation when ch... Open
split to UXPROD-3864 Warn and require confirmation when ch... Open
split to UXPROD-3868 In the Inventory app, allow items wit... Open
Epic Link: Item states (status)
Front End Estimate: Large < 10 days
Back End Estimate: XL < 15 days
Back End Estimator: Marc Johnson
Development Team: Prokopovych
PO Rank: 100
PO Ranking Note: These statuses are already in the system, and it's problematic to have them exist without the intended behavior.
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or problem:
Order closed is an existing item status, but the Check Out, Check In, Requests, and Inventory apps don't respond to this status in desired ways.

  • Inventory: Currently, an item with the item status Order closed cannot be made missing, withdrawn, etc.
  • Check Out: Currently, FOLIO allows check out without warning
  • Check In: Currently, FOLIO allows check in without warning
  • Requests: Currently, FOLIO allows requests on this status

In scope

  • Inventory: Allow users to change the status of Order closed items manually to any status except one that indicates an item is loaned (e.g., checked out). Do not link to new request from actions menu in Inventory Moved to UXPROD-3868 Open
  • Check Out: Require confirmation of check out if user is checking out item with item status order closed, and warn if the item is suppressed from discovery moved to UXPROD-3683 Closed
  • Check In: Require confirmation of check in if user is checking out item with item status order closed, and warn if the item is suppressed from discovery moved to UXPROD-3864 Open
  • Requests: Prevent requests on items with this status moved to UXPROD-3862 Open

Out of scope

  • Previously, this feature included stories about cleaning up the In process status. However, the stories for that has either been moved to UXPROD-2699 Closed or closed as duplicates.

Use case(s)

Proposed solution/stories
UXPROD-3682 Closed - disallow requesting

Links to additional info

Questions



 Comments   
Comment by Emma Boettcher [ 27/May/20 ]

Marc Johnson Michal Kuklis could you estimate this when you have a minute? Thank you!

Comment by Marc Johnson [ 28/May/20 ]

Emma Boettcher I'm not sure I follow the scope of this feature, is it purely to introduce the Order closed item status and account for that during circulation processes?

Comment by Emma Boettcher [ 28/May/20 ]

Marc Johnson Order closed is already a status, so this feature is to make sure Check In, Check Out and Requests handle that appropriately.

In process is also already a status, but this feature also includes a story allowing users to manually set an item status to In process in Inventory (like Withdrawn or Missing).

Comment by Emma Boettcher [ 12/Jun/20 ]

Michal Kuklis when you have a minute, could you add a front-end estimate to this one? Happy to answer any questions if needed.

Comment by Michal Kuklis [ 12/Jun/20 ]

Sorry Emma Boettcher I missed this. Is the scope for this similar to what we have done for other statuses on the UI side across multiple modules?

Comment by Emma Boettcher [ 12/Jun/20 ]

Michal Kuklis Yep! The linked issues have more info.

Comment by Michal Kuklis [ 12/Jun/20 ]

Emma Boettcher Thank you. I just updated the estimate. I think it could actually take less time for somebody who already worked on the previous stories.

Comment by Erin Nettifee [ 20/Oct/22 ]

This was a large feature - I went ahead and split it into four features to make it more likely to get worked on.

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