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

Lost items requiring ACTUAL COST: Generate 'skeleton' list of items

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 148, EPAM-Veg Sprint 149
    • 5
    • Vega
    • Nolana R3 2022

    Description

      User story updated on May 27, 2022

      This user story has been updated due to design changes to the following pages...

      • ACTION menu from the Users App was reorganized (see updated attachment 1-users-actions-button-lost-items.png)
      • ACTION column on the processing page was changed from just a Process" button to an ellipsis with 4 options: Bill actual cost, Patron details, Loan details and Item details (see updated attachments SKELETON-2-lost-items-requiring-actual-costs.jpg and 2-lost-items-requiring-actual-costs.png)--the ellipsis options have replaced the in-column links
      • Instance column cuts off the title at three lines and then displays ... to see full title (see attachment 6-show-long-title.png)

      Note: Scenarios 8-12 are new!

      User story split on September 25, 2020

      Due to the size of UIU-1382 (Declared Lost/Aged to Lost: Generate 'report' of lost items requiring actual cost ), Holly was asked by the devs to split the user story into multiple smallers stories:

      • UIU-1382 (Lost items requiring ACTUAL COST: Generate 'skeleton' list of items)
      • UIU-1866 (Lost items requiring ACTUAL COST: Implement searching)
      • UIU-1867 (Lost items requiring ACTUAL COST: Implement 'Loss type' filtering)
      • UIU-1868 (Lost items requiring ACTUAL COST: Implement 'Fee/fine owner' filtering)
      • UIU-1869 (Lost items requiring ACTUAL COST: Implement 'Date of loss range' filtering)
      • UIU-1870 (Lost items requiring ACTUAL COST: Implement additional information in 'Patron' column)
      • UIU-1871 (Lost items requiring ACTUAL COST: Implement additional information in 'Instance' column)
      • UIU-1880 (Lost items requiring ACTUAL COST: Implement additional searching) <== created on September 29, 2020

      Note: Each front-end story has a corresponding back-end story.

      User story split on September 24, 2020

      Due to the size of UIU-1382 (Declared Lost/Aged to Lost: Generate 'report' of lost items requiring actual cost ), Holly has split the user story into two stories:

      • UIU-1382 (Declared Lost/Aged to Lost: Generate 'report' of lost items requiring ACTUAL COST) - this user story will create the list of items to process and address the searching and filtering
      • UIU-1863 (Declared Lost/Aged to Lost: Bill patron for ACTUAL COST of lost item) - this user story will actually bill the patron from the lost item's actual cost

      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 SKELETON-2-lost-items-requiring-actual-costs.png 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 Users app Users search results page Actions drop-down
        • When open
        • Then show new drop-down option Lost items requiring actual costs as shown in attached mock-up 1-users-actions-button-lost-items.png (please note that the ACTIONS menu has also been reorganized)
      2. Scenario
        • Given the backend search for items completed
        • When no items found matching the criteria
        • Then:
          • Open Lost items requiring actual costs page (as shown in attached mock-up SKELETON-2-lost-items-requiring-actual-costs.jpg), displaying: No results found. (in gray text, in the middle of the results page, similar to what FOLIO currently does when searching for users (see attached example No-users-found-search-example.jpg))
          • Display '0 records found' on top of page (as shown in attached mock-up SKELETON-2-lost-items-requiring-actual-costs.jpg)
      3. Scenario
        • Given the backend search for items completed
        • When items found matching the criteria
        • Then open Lost items requiring actual costs page (as shown in attached mock-up SKELETON-2-lost-items-requiring-actual-costs.jpg) with most recent lost items (Date of loss) appearing on top of the page
          • Page columns
            • Patron column
              • Last name, First name Middle name (from User information record)
            • Loss type column
              • Item status (from the Item record)
            • Date of loss column
              • Date the item was declared lost or aged to lost. This date is available in the Loan 'Action' record by looking for the 'Action' record with an Action of 'Declared lost' or 'Aged to lost' and then grabbing the Action date
            • Instance column
              • Title (Material type) (from Item record) Instead of the full Title, display 75 characters of Title, with ... representing more (clicking on ... will present entire Title plus Material type (as shown in attached mock-up 6-show-long-title.png))
            • Permanent item location column
              • Item location: Permanent from the Location section of the Item record
            • Fee/fine owner column
              • Fee/fine owner is derived from the Item location: Permanent by using this location to find the Primary service point and then seeing which Fee/fine owner is associated with that Primary service point at Settings>Users>Fee/fine: Owners
            • Fee/fine type column
              • 'Automatic' Fee/fine type from the Manual charges table at Settings>Users>Fee/fine: Manual charges (for ACTUAL COST this is 'Lost item fee (actual cost))
            • Actions column includes ellipsis with these options...
              • Bill actual cost
              • Patron details
              • Loan details
              • Item details
          • Insert number of records returned where '# records found' is to be displayed on top of page (as shown in attached mock-up SKELETON-2-lost-items-requiring-actual-costs.jpg)
          • Display "Search & filter" section on left
      4. Scenario
        • Given the Lost items requiring actual costs page
        • When column heading is clicked on a previously unsorted column (except for ACTIONS column, which is not sortable)
        • Then sort by the database name of the first field in the column, in ascending order, flipping the sort icon from down arrow to up arrow
      5. Scenario
        • Given the Lost items requiring actual costs page
        • When column heading is clicked on a previously sorted column (except for ACTIONS column, which is not sortable)
        • Then sort by the database name of the first field in the column, in opposite order, flipping the sort icon as needed
      6. Scenario
        • Given the Lost items requiring actual costs page
        • When ellipsis ACTION option "Patron details" is selected
        • Then open User Details page for the patron
      7. Scenario
        • Given the Lost items requiring actual costs page
        • When ellipsis ACTION option "Loan details" is selected
        • Then open Loan Details page for the lost item
      8. Scenario
        • Given the Lost items requiring actual costs page
        • When ellipsis ACTION option "Item details" is selected
        • Then open Item Details page for the lost item
      9. Scenario
        • Given the Lost items requiring actual costs page
        • When Instance title is more than 75 character long
        • Then cut the title off at 75 characters and add ... icon as a way to display entire title
      10. Scenario
        • Given the Lost items requiring actual costs page
        • When Instance column icon ... selected
        • Then show expanded title as shown in attached mock-up 6-show-long-title.png)

      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:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases