Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines (UXPROD-1146)

[UIREC-122] Receiving app does not support searching POLs without a prefix Created: 06/Apr/21  Updated: 06/Jul/21  Resolved: 08/Apr/21

Status: Closed
Project: ui-receiving
Components: None
Affects versions: None
Fix versions: 1.3.2, 1.4.0
Parent: Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines

Type: Bug Priority: P3
Reporter: Molly Driscoll Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: receiving, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-2169 Thunderjet - R1 2021 Enhancements/Bug... Closed
Requires
requires UIREC-119 Receiving: Add option to search by Ve... Closed
Sprint: ACQ Sprint 112
Story Points: 0
Development Team: Thunderjet
Affected Institution:
MI State University/Library of Michigan
Epic Link: Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines

 Description   

Overview: If an order has a prefix assigned to it, the receiving app does not allow searching for that PO line without including the prefix. This is different from behavior in the orders app, where an order can be searched with or without a prefix included.

This issue was raised by Michigan State University (currently on Honeysuckle HF #3), and reproduced on Bugfest Iris.

Steps to Reproduce: (bugfest)

  1. Log into https://bugfest-iris.folio.ebsco.com/ as a user with permissions in the orders/receiving app.
  2. Open the Orders app.
  3. In the order lines search, search for 14059.
    1. Notice you get one result for lawmono14059-1.
  4. Open the Receiving app.
  5. Search for 14059.

Steps to Reproduce: (folio-snapshot)

  1. Go to Settings/Orders/PO number/Prefixes
  2. Create an order prefix
  3. Go to the Orders app and create a PO and POL using that PO prefix
  4. Open the order
  5. Search for the POL in the orders app with and without the prefix (in Keyword and POL searches)
  6. Go to the Receiving app
  7. Search for the POL in the receiving app with and without the prefix (in Keyword and POL searches)

Expected Results: You receive the same results as in the Orders app (one result for lawmono14059-1). Searching for POL in the Orders and Receiving apps in the Keyword and POL searches should be consistent, and as tolerant as possible (i.e. "contains" instead of "begins" or exact)

Actual Results:  No results found. You need to search lawmono14059 (bugfest) to access that POL for receiving. It seems like the Orders app treats the POL as a Begins or Contains search, but Receiving only treats it as a Begins or Exact search

Interested parties:

Molly Driscoll

Kay Granskog



 Comments   
Comment by Molly Driscoll [ 06/Apr/21 ]

Ann-Marie Breaux tagging you for awareness because I know you're currently covering for Dennis Bridges.

Comment by Ann-Marie Breaux (Inactive) [ 07/Apr/21 ]

Hi Molly Driscoll or Anya Could you remind me - we can change this SUP ticket to the appropriate UI or MOD project, as long as we leave the label "support" on it. Is that right?

Comment by Ann-Marie Breaux (Inactive) [ 07/Apr/21 ]

Reproduced the bug in folio-snapshot, updated the description and the project. Checking with the Tjet devs on whether this is UI-only and if we can fit into Iris bugfixes

Comment by Molly Driscoll [ 07/Apr/21 ]

Ann-Marie Breaux thanks for looking into this! I confirmed it still appears on the Support SIG dashboard even with the project change.

Comment by Victoria_Smelova [ 07/Apr/21 ]

Fixed in scope of UIREC-119 Closed .
To be tested when UIREC-119 Closed is completed.

Comment by Ann-Marie Breaux (Inactive) [ 08/Apr/21 ]

Hi Former user and Mikita Siadykh Tested on folio-snapshot-load, and it works perfectly in the Keyword, PO, and POL searches, with and without a prefix. I'll move this to awaiting release, and have made a note to add a Testrail for it.

Comment by Dennis Bridges [ 29/Apr/21 ]

Test successful in bugfest-iris

Generated at Thu Feb 08 22:21:35 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.