Uploaded image for project: 'mod-orders-storage'
  1. mod-orders-storage
  2. MODORDSTOR-304

Implement logic for updating Piece fields when Item was changed

    XMLWordPrintable

Details

    • Story
    • Status: Open (View Workflow)
    • P3
    • Resolution: Unresolved
    • None
    • None
    • 3
    • Thunderjet

    Description

      Purpose/Overview:
      Implement a event consumer that responds to Item changes in the inventory

      Requirements/Scope:

      1. Updated fields (displayOnHolding, enumeration, chronology, discoverySuppress) from Item should be reflected in the Piece
      2. Open question : : dennisbridges Should we update Received piece or only Expected? (yes we should update Received piece)

      Approach:

      • Create handler of the Item update event
      • Implement logic for stubbed method from MODORDERS-560
      • If message is broken, then log as ERROR

      Acceptance criteria:

      • Update Piece logic implemented
      • Unit tests
      • API tests

      TestRail: Results

        Attachments

          Issue Links

            blocks

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

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

            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
            has to be done after

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-559 Spike : Analyze domain event pattern implementation

            • 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. MODORDSTOR-303 Implement Kafka event consumer in mod-orders-storage

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

            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

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

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

            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
            mentioned in

            Page Loading...

            Activity

              People

                Unassigned Unassigned
                Andrei_Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases