Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-1867

Lost items requiring ACTUAL COST: Implement filtering by 'Loss type'

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 149, EPAM-Veg Sprint 150
    • 3
    • Vega
    • Nolana (R3 2022)

    Description

      Purpose: Request a list of lost items requiring actual cost and then bill the patron a lost item fee.

      Story: As a staff member who charges patrons for lost items, I need a list of items to have selectors find the replacement price for and then bill the patron for that amount.

      Special note: Attached mock-up LTFILTER-2-lost-items-requiring-actual-costs.jpg is the one that should be used for this user story. Attached mock-up 2-lost-items-requiring-actual-costs.png is provided to show what the page will look like after all of the related user stories have been completed.

      Scenarios:

      1. Scenario
        • Given the Lost items requiring actual costs page
        • When open
        • Then display Loss type filter (as shown in attached mock-up LTFILTER-2-lost-items-requiring-actual-costs.png), plus the rest of page as it currently is displayed (only two Loss types are available: "Aged to lost" and "Declared lost")
      2. Scenario
        • Given the Lost items requiring actual costs page
        • When one or both Loss types selected to filter by (by check marking the appropriate filter box)
        • Then limit items presented in list to those meeting this specific criteria
      3. Scenario
        • Given the Lost items requiring actual costs page
        • When RESET button presses
        • Then clear the search/filters and display list as presented before searching/filtering

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Dmitriy Litvinenko Dmitriy Litvinenko
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases