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

Display Holding OR Location name in location column in search results

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 2.0.0
    • ACQ Sprint 124
    • 1
    • Thunderjet
    • R3 2021

    Description

      Overview: When reviewing search results in the receiving app, instead of showing the proper Holdings location in the search results, the location displays as "invalid reference".

      Scenario:

      • Given user has opened a POL that now references one or more Holdings
      • When viewing the related "Receiving titles" in the search result list
      • Then the location column shows the related Holdings Name(s)

       

      Steps to Reproduce:

      1. Log into folio-snapshot as diku_admin
      2. Go to the Orders app
      3. Create an order that has Inventory = create instance, holdings, item, and Manually create pieces is NOT checked. As part of creating the POL, you will assign 1 or more locations to the POL.
      4. Open the order
      5. Go to the receiving app
      6. Look up the title of the POL that you just created
      7. Review the Location information in the search results

      Expected Results: The proper location(s) shows in the Location column of the search results based on the Holdings UUID

      Actual Results: It shows "invalid reference" as there is no Location UUID present for this order.

      Additional Information: See attached video

      TestRail: Results

        Attachments

          1. Proof_1.png
            Proof_1.png
            164 kB
          2. Proof_2.png
            Proof_2.png
            92 kB
          3. UIREC-172 bug.mp4
            2.32 MB

          Issue Links

            Activity

              People

                dennisbridges Dennis Bridges
                abreaux Ann-Marie Breaux
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases