Revise the Orders search results list columns

Description

Overview: When search results display for PO searches and filters, this story describes what columns and data should appear

Scenarios

  1. Scenario 1

    • Given the Orders app landing page

    • When a user searches or filters for POs

    • Then the results pane should include the following columns:

      • PO number

      • Vendor [display the vendor code, not the vendor name]

      • Status

      • Order type

      • Last updated [date only, no time]

      • Acquisitions unit [previously Owner] (DB: Must be split out into separate issue)

      • Assigned to

  2. Scenario 2

    • Given the PO search results list

    • When a user first switches from the POL toggle to the PO toggle

    • Then the results list should be filtered to only display POs that are

      • Pending or Open

      • Which means that POs that are Closed are not displayed by default

  3. Scenario 3

    • Given the PO search results list

    • When a user views the PO search results list

    • Then the user should be able to sort the results list ascending and descending by clicking on the following column headers

      • PO number

      • Status

      • Order type

      • Last updated

    • And the default sort order should be descending by PO number (numerics descending, then alphas descending)

    • Note: sorting for the Vendor, Acquisitions unit, and Assigned to columns will be handled separately, in story https://folio-org.atlassian.net/browse/UIOR-308#icft=UIOR-308. For those 3 columns, suppress the up/down sort arrow next to the column header.

  4. Scenario 4

    • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges July 4, 2019 at 7:46 PM

when you return pls take a look at the default sort order for PO. You have requested descending but I'm unclear how to interpret that, I believe it is currently in correct but I'm not certain so I will resolve it for now and if you confirm next week pls create a bug for the adjustment. Thx!

Aliaksei Chumakou July 2, 2019 at 10:29 AM

checked on testing

Dennis Bridges June 28, 2019 at 5:30 PM

for now I have split the display of Acquisition unit out into a separate story https://folio-org.atlassian.net/browse/UIOR-310#icft=UIOR-310 so that we can work on this issue

Aliaksei Chumakou June 28, 2019 at 10:07 AM
Edited

In previous requirements it was just owner or unit, single select value. Now it's plural, and it's not a part of Orders list API response. That's why now is complicated to display that column.
Maybe we need to discuss the reason to display this, I don't think that additional API call for every row will work well

Dennis Bridges June 27, 2019 at 9:34 PM

I gather this is the case because Acq units are a separate API and we will have this issue with any record we assign a team too. Eg. Order, Invoice, Fund etc.?

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 17, 2019 at 3:17 PM
Updated September 17, 2019 at 8:38 PM
Resolved July 4, 2019 at 7:47 PM
TestRail: Cases
TestRail: Runs