Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3342

Implement data consistency approach for Piece<>Item interaction

    XMLWordPrintable

Details

    • 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 

      Approach

      See MIRO Board

      TestRail: Results

        Attachments

          Issue Links

            is cloned by

            New Feature - New feature requests UXPROD-3879 Implement data consistency approach for Item<>Piece interaction

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-569 Implement logic for updating Item fields when Piece was changed

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-807 Copy number does not get applied to item when creating item through receiving app

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREC-148 Data consistency - Update Item when piece Enumeration and Chronology are updated

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

            Umbrella - UXPROD-1647 Theme: Ability to maintain relationships between other apps when holdings/items are moved

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

            Page Loading...

            Activity

              People

                dennisbridges Dennis Bridges
                dennisbridges Dennis Bridges
                Raman Auramau Raman Auramau
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases