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

Manual charge with item should not be associated with loan

    XMLWordPrintable

    Details

    • Template:
      Standard Bug Write-Up Format
    • Sprint:
      EPAM-Veg Sprint 94, EPAM-Veg Sprint 95, EPAM-Veg Sprint 96
    • Story Points:
      1
    • Development Team:
      Vega
    • Release:
      Q2 2020 Hot Fix #1

      Description

      There are two ways for libraries to associate a manual fee/fine to a loan:

      1. On the Checkin page, select New fee/fine from the ellipsis menu--this will automatically fill in the item information on the New Fee/Fine page
      2. On the Loan History page, select New fee/fine from the ellipsis menu--this will automatically fill in the item information on the New Fee/Fine page

      In 99.99% of cases, this is how a patron will be charged for missing pieces and damaged items.

      If a loan record no longer exists, but the library wants to change the patron for missing pieces and damaged items, the library has the option to use the Barcode to charge the patron directly via the New Fee/Fine page. This approach will not have a loan record link, but will have item information available.

      Holly has just learned that the original developer included code to link the fee/fine to a loan record that matches the item id, making a guess if there are more than one. (See attached Slack message.) This should not be done given that:

      1. This approach should only be used when a loan record does NOT exist
      2. There can be more than one loan record and we should NOT guess which one is the correct one

        TestRail: Results

          Attachments

            Activity

              People

              Assignee:
              maxim_didenko Maxim Didenko
              Reporter:
              hollyolepm Holly Mistlebauer
              Tester Assignee:
              Holly Mistlebauer Holly Mistlebauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  TestRail: Runs

                    TestRail: Cases