Uploaded image for project: 'ui-receiving'
  1. ui-receiving
  2. UIREC-148

Data consistency - Update Item when piece Enumeration and Chronology are updated

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • None
    • None
    • ACQ Sprint 132, ACQ Sprint 133, ACQ Sprint 134
    • 0
    • Thunderjet

    Description

      Purpose: In order to display piece details on holding records users will need a mechanism to indicate that they want this to happen. This will give users the choice to display piece information on holding. Updating the caption field will allow users to capture information that is more consistent with the inventory app. This will improve workflow between receiving and cataloging.

      User story statement(s):

      As a receiving staff member,
      I want to be able to tell system to display info on holding
      so that I do not need to manually enter duplicate information into the inventory app

      Scenarios:

      1. Update Item from Piece
        • Given piece is connected to item record
        • When editing or creating piece
        • Then Enumeration and Chronology fields update the corresponding fields in the item record
      2. Update Piece from Item (Moved to UIREC-225)
        • Given piece is connected to item record
        • When editing Item
        • Then the corresponding fields are updated in the piece

      TestRail: Results

        Attachments

          Issue Links

            clones

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREC-135 Update create, edit and receive piece forms with additional fields

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

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

            • P2 - normal priority level, must be included in the current development cycle
            • In Review
            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. 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. MODORDSTOR-235 Add field to Piece schema for support holding

            • TBD - To be determined
            • Closed

            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

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

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

            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-534 Define and implement business API for retrieving pieces information

            • 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-535 Take into consideration "holdingId" or "locationId" when check-in/unreceive/receive pieces

            • 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. MODORDSTOR-240 Add new fields to receiving history view: displayOnHolding, enumeration, chronology, discoverySuppress

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

            Page Loading...

            Page Loading...

            Activity

              People

                Unassigned Unassigned
                dennisbridges Dennis Bridges
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases