Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3377

Loan: (FE) Lost Item Fees processing page for ACTUAL COST

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Release:
      Not Scheduled
    • Epic Link:
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      Out of scope
    • Front-End Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Re-estimated by Vega 12/14/21

      New back end developers are still getting used to working in the team (and FOLIO) and are all unfamiliar with this area. It could easily take much longer than 45 days.

      If this work includes new APIs, then this estimate will likely need to grow in order to accommodate the expectation for API integration testing with Karate.
      Show
      Re-estimated by Vega 12/14/21 New back end developers are still getting used to working in the team (and FOLIO) and are all unfamiliar with this area. It could easily take much longer than 45 days. If this work includes new APIs, then this estimate will likely need to grow in order to accommodate the expectation for API integration testing with Karate.
    • Development Team:
      Vega
    • Calculated Total Rank:
    • Kiwi Planning Points (DO NOT CHANGE):
      71
    • PO Rank:
      96
    • Rank: Chicago (MVP Sum 2020):
      R5
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R2
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: GBV (MVP Sum 2020):
      R5
    • Rank: Grand Valley (Full Sum 2021):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R3
    • Rank: MTSU:
      R2
    • Rank: MI State-Lib of MI (Sum 2021):
      R2
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Split February 15, 2022 to create FE and BE separate features

      Split on October 20, 2021

      Formerly UXPROD-2391 included both the ACTUAL COST fee/fine work for items that are Declared Lost and the report that will be used to process the ACTUAL COST for both Declared Lost and Aged to Lost items. Holly split the processing report since it is for both Declared Lost and Aged to Lost items. UXPROD-2391 now covers only the ACTUAL COST fee/fine work for items that are Declared Lost. UXPROD-3377 covers the processing report.

      Redesigned on September 23, 2020

      The redesign of the ACTUAL COST process has resulted in no longer needing the following user stories...

      • UIU-1593 (Declared lost item: Manual fee setting for ACTUAL COST fee/fine type)
      • MODFEE-51 (BE - Declared lost item: Manual fee setting for ACTUAL COST fee/fine type)
      • CIRC-727 BE - (Declared lost: renewal (effect on lost item fees) - SHARED ACTUAL COST)
      • CIRC-729 BE - (Declared lost item: check in (effect on fines/fees) - SHARED ACTUAL COST)

      The following user stories will be kept, but have been renamed...

      • CIRC-728
        • OLD: BE - Declared lost: renewal (effect on lost item fees) - FF OWNER ACTUAL COST
        • NEW: BE - Declared lost: renewal (effect on lost item fees) - ACTUAL COST
      • CIRC-730
        • OLD: BE - Declared lost item: check in (effect on fines/fees) - FF OWNER ACTUAL COST
        • NEW: BE - Declared lost item: check in (effect on fines/fees) - ACTUAL COST
      Merged on July 20, 2020

      UXPROD-846 (Fees/Fines in-app report: Lost items requiring actual cost) was merged with UXPROD-2391 (Lost: Declared Lost - Fee/Fine work for ACTUAL COST) to create UXPROD-2046 (UXPROD-2391 (Lost: Declared Lost - Fee/Fine work for ACTUAL COST). Note: This was done because of the constant misunderstanding that the report wasn't a high priority although it was part of the thin-thread workflow.

      Split on April 22, 2020

      UXPROD-2246 Loan: Declared Lost - Fee/Fine work was split into two features:

      1. UXPROD-2246 Loan: Declared Lost - Fee/Fine work for SET COST (for Q2 2020)
      2. UXPROD-2391 Loan: Declared Lost - Fee/Fine work for ACTUAL COST (for later in 2020 or Q1 2021)

      Update 2/11/22, clarifying questions:

      UIU-1382
      1. Could you please confirm that button "Lost items requiring actual costs" should be at the bottom of "Actions drop-down"?
      A: Yes, confirmed Holly has updated Scenario 1 to indicate that the new option should be at the bottom and has attached a new mock-up to UIU-1382.
      2. Could you please confirm that we have "Lost Item Fees processing page for ACTUAL COST" and we don't have any report?
      A: There is no report - it is a processing page Holly has removed all references to "report" from the scenarios.
      3. Could you please confirm that "2. Scenario" this is search rules for BE?
      A: Already in the backend story, so it can be removed from FE story, BE story must be done first. Holly has removed the scenario from the front-end story and has added a link to CIRC-940.
      4. Can we move Scenario 6-7 to a separate story and discuss them separately (just for example: we have a patron name and a patron barcode and we need to know what field we need to use for sorting)?
      A: Holly will move to separate story. Translate to other languages. Make sure scope is clear that sorted by database name, but not by local alphabetization Holly has created a brief story (CIRC-1440) for this and will clarify it when it is scheduled to be worked on (in Nolana).
      5. Could you please confirm that data selected red cannot be localized and all other data should be localized (localization.jpg)?
      A: Yes, confirmed, though dates should be confirmed. Holly will add to this story. Holly has added a note to this user story.

      UIU-1863
      Holly will describe images within story scenarios.

      1. Could you please confirm that "Actual cost to bill patron" greater or equal 0.00 and less or equal 9999.99 (3-charge-fee-modal.png)?
      A: Confirmed, Holly will add to story Holly has updated scenario 3 to reflect this requirement.
      2. Could you please confirm that we always should show 2 decimal places for "Actual cost to bill patron" (3-charge-fee-modal.png)?
      Confirmed, Holly will add to story Holly has updated scenario 1 to reflect this requirement.
      3. Could you please confirm that input "Actual cost to bill patron" should use full column width (3-charge-fee-modal.png)?
      Confirmed, Holly will add to story Holly has updated 3-charge-fee-modal.png to reflect the column width.
      4. Could you please describe what we need to show in "Error toast" (just for example 2 people can try "Charge" one item) (5-charge-fee-success.png)?
      Holly will add to story Holly has added a scenario for this situation to the user story.
      5. Could you please confirm that "Billed: <billed amount>" should be black and bold (5-charge-fee-success.png)?
      Confirmed, Holly will add to story Holly has updated 5-charge-fee-success.png to show Billed: 0.00 in bold black instead of bold blue.
      6. Could you please confirm that for modal 4-confirm-modal.png we should change text for button from "Charge fee" to "Billed" (4-confirm-modal.png)?
      Holly will clarify and add to story No, that isn't the change Holly made in the end. Holly changed the "Charge fee" button on 2-lost-items-requiring-actual-costs.png to "Process" and the "Charge fee" button on 4-confirm-modal.png to "Confirm & save". The "Charge fee" button on 3-charge-fee-modal.png will remain as "Charge fee". The updated mock-ups have been attached to the user story.

      UIU-2491
      1. Could you please confirm that button "Lost items requiring actual costs" ( https://issues.folio.org/browse/UIU-1382 ) not visible when user don't have this permission?
      A: Holly will add to story Holly has added this note to the user story.
      2. Could you please confirm that we have "Lost Item Fees processing page for ACTUAL COST" and we don't have any report?
      A: Holly will add to story Holly has changed all references to "report" to "processing page".

      Pagination issue/story is missing. Pavel is working on a PoC. UIU-2519. Pavel recommends option 2, but is unsure of the time required to implement. Further investigation needed. This can be done for Nolana.
      Solution 3, Load more...approach will be acceptable for Morning Glory. How many items should load at one time? 100. Holly has created user story CIRC-1441 for pagination. It is in draft form until the approach is defined.

      Holly will come up with scenarios for karate tests - happy path scenarios. Performance needs to be defined as well. Holly will ask Users. Holly will also write test cases in test rails. Holly has Karate tests, performance and Test Rail test cases on her list of things to do.

      Additional update 2/11/22, from Holly:

      • Holly was also asked to add one filter to the first release of this so that there is something in the left-hand column. Holly will add "Loss type". Holly has added CIRC-942 and UIU-1867 to this story.
      • Holly has realized that she needs to add a story for when aged to lost/declared lost items are returned or renewed. They should be removed from the list of items needing actual cost. Holly has created one story for returned items and one story for renewed items. They are CIRC-1444 and CIRC-1445.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                hollyolepm Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases