Details
-
New Feature
-
Status: In Refinement (View Workflow)
-
P2
-
Resolution: Unresolved
-
None
-
None
-
-
Medium < 5 days
-
XL < 15 days
-
80%
-
We need to think about splitting stories based on Moving item vs moving Holdings.
-
Thunderjet
-
-
55
-
R2
-
50%
Description
Overview:
Receiving updates in UXPROD-2373 and UXPROD-1925 have added additional reference points between orders and inventory records. They have also added fields to the piece record that must be reflected in related item records. When user edits these fields in either the item or the piece record the other must be updated so the data remains consistent in both modules.
Use cases:
See wiki page: https://wiki.folio.org/x/DAS-BQ
TestRail: Results
Attachments
Issue Links
- is defined by
-
MODORDERS-559 Spike : Analyze domain event pattern implementation
-
- Open
-
-
MODORDERS-569 Implement logic for updating Item fields when Piece was changed
-
- Closed
-
-
MODORDERS-642 Data corruption. When holding/item data are moved in Inventory, then the connected Order lines are not updated accordingly
-
- In Refinement
-
-
MODORDSTOR-303 Implement Kafka event consumer in mod-orders-storage
-
- Open
-
-
MODORDSTOR-304 Implement logic for updating Piece fields when Item was changed
-
- Open
-
-
UIREC-148 Data consistency - Update Item when piece Enumeration and Chronology are updated
-
- Closed
-
-
UIREC-225 Data consistency - Update Piece when Item Enumeration and Chronology are updated
-
- Blocked
-
- relates to
-
UXPROD-1647 Theme: Ability to maintain relationships between other apps when holdings/items are moved
-
- Open
-
- mentioned in
-
Page Loading...