Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
Core: F - Sprint 71, Core: F - Sprint 72, Core: F - Sprint 73, Core: F - Sprint 74, Core: F - Sprint 75
-
Prokopovych
Description
Background: We originally pointed the Filter by effective location story (UIIN-199) for the ui-only approach. After looking into it, it was concluded (see issue comments) that we would move this filter work out of Q3.2 so we could "experiment with the UI version if we want, whilst progressing the stored version in the backend.".
So the scope of this story is whatever backend work is needed to progress the backend option.
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-199 Filter by the effective location
-
- Closed
-
- defines
-
UXPROD-140 Q4 2019 Timebox for Priority Inventory Search and Filter Enhancements
-
- Closed
-
- has to be done before
-
CIRC-473 Use stored effective location for item
-
- Closed
-
-
MODINV-157 Handle new effectiveLocationId property for item
-
- Closed
-
- is blocked by
-
MODINVSTOR-364 holdingsRecord.permanentLocationId is required field
-
- Closed
-
- relates to
-
CIRC-532 [SPIKE/FEATURE]: Refactor tests to be less dependent on the item effectiveLocationId logic
-
- Closed
-
-
MODINVSTOR-277 SPIKE: filtering by Effective Location
-
- Open
-
-
MODINVSTOR-378 Use PgUtil.post util with INSERT ... RETURNING jsonb from RMB in ItemStorageAPI#postItemStorageItems
-
- Closed
-
-
RMB-476 PgUtil.post: Return after-trigger value (INSERT ... RETURNING jsonb)
-
- Closed
-