Create the primary filter options for Orders

Description

Overview: Until the PO/POL search results can be displayed in a hierarchical view, we will show the PO and POL search results separately. This story describes the filter options for POs that are most urgent to implement. Secondary, less-urgent options are described in UIOR-266. Users need the ability to search and filter orders by a number of different field values. This will help them find exactly what they are looking for and what they should be working with.

There is a column in this Google sheet marked "Filter on This?" (column I) which identifies the fields that should appear as filter options. There is a tab for each App so you will need to navigate to the "Order" tab in this sheet for order fields, and only pay attention to the green filter options for the PO, not the yellow or the POL. https://docs.google.com/spreadsheets/d/1F88PoSnEKD7oFnza1ZuOgzAgKnK95XOyTQzxyww3tZA/edit#gid=1408113181

  1. Scenario 1

    • Given the Orders app landing page

    • When a user wants to filter within POs (the purchase order toggle is highlighted)

    • Then they should see the following options in the filters area, in this order:

      • Status

      • Date ordered (by date range)

      • Order type

      • Vendor (Vendor name, followed by Vendor code in parentheses)

      • Renewal date (by date range)

      • Renewal manual

      • Renewal review period (Text field filter for integer)

    • And all filter accordions should be closed except for Status [workflow status], [since that filter is used in UIOR-269 as the default filter when the PO toggle is first opened]

    • And results should be displayed as indicated in UIOR-269

  2. Scenario 2

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

NOTE Filtering by tags is also high priority for Chalmers, but cannot be implemented until after tags are implemented. See separate story UIOR-279 for adding filtering by tags.

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges June 5, 2019 at 9:46 PM

test successful in folio-testing.

Mikita Siadykh June 4, 2019 at 6:56 PM

hi

tested on https://folio-testing.aws.indexdata.com, please review

SS with result

coverage > 80%

Marie Widigson May 28, 2019 at 12:57 PM

Hi I think this is a go-live issue for us. Please get back to us if you have any question.

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:14 PM
Updated July 2, 2019 at 7:36 AM
Resolved June 5, 2019 at 9:46 PM
TestRail: Cases
TestRail: Runs