Item states (status) (UXPROD-1321)

[UXPROD-3898] Customize built-in item statuses: Data Import Created: 15/Nov/22  Updated: 21/Nov/22

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

Type: New Feature Priority: P4
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Issue split
split from UXPROD-2606 Item status: Check in - Customize beh... Draft
Epic Link: Item states (status)
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 78
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R4
Rank: MO State (MVP June 2020): R4
Rank: U of AL (MVP Oct 2020): R3

 Description   

Current situation or problem:
Many apps can change item status, but tenants cannot control how these apps interact with built-in item statuses.

In scope

  • Customize behavior of built-in item statuses in Data Import

Out of scope

  • Allowing tenants to create new item statuses ( UXPROD-1535 Draft )
  • Customizing behavior for Orders, Receiving, and Requests ( UXPROD-2635 Draft , UXPROD-1320 Closed )
  • Customizing name, discovery display name, and ability to deactivate ( UXPROD-2636 Draft )
  • Changes in circ rule behavior. Currently, if the circ rule allows something but the item status doesn't, the item status wins. If the circ rule doesn't allow something but the item status does, the circ rule wins. Essentially, a conflict defaults to not allowing.

Use case(s)

  • A library does not want to use a built-in item status, and so they mark it inactive ( UXPROD-2636 Draft ). In Data Import, that item status does not show up in any of the UI mapping profiles.

Proposed solution/stories

  • UX story for UXPROD-1535 Draft has a mockup of how this could look (for both built-in and custom item statuses)

Links to additional info

Questions


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