Uploaded image for project: 'mod-inventory-storage'
  1. mod-inventory-storage
  2. MODINVSTOR-348

UIIN-199: Filter by Effective Location: Save Effective Location on Item Record

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 18.0.0
    • 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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-199 Filter by the effective location

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            defines

            New Feature - New feature requests UXPROD-140 Q4 2019 Timebox for Priority Inventory Search and Filter Enhancements

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-473 Use stored effective location for item

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINV-157 Handle new effectiveLocationId property for item

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            Bug - A problem which impairs or prevents the functions of the product. MODINVSTOR-364 holdingsRecord.permanentLocationId is required field

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-532 [SPIKE/FEATURE]: Refactor tests to be less dependent on the item effectiveLocationId logic

            • TBD - To be determined
            • Closed

            New Feature - New feature requests MODINVSTOR-277 SPIKE: filtering by Effective Location

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-378 Use PgUtil.post util with INSERT ... RETURNING jsonb from RMB in ItemStorageAPI#postItemStorageItems

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. RMB-476 PgUtil.post: Return after-trigger value (INSERT ... RETURNING jsonb)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                bohdan-suprun Bohdan Suprun
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases