Uploaded image for project: 'ui-checkin'
  1. ui-checkin
  2. UICHKIN-11

Check-in takes more than 2 seconds per item

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      Prokopovych

      Description

      Overview: Check-in of multiple items is too slow.

      How to reproduce:
      Open http://folio-snapshot-stable.aws.indexdata.com/checkin
      Enter the barcode of a loaned item.
      Press the enter key or press the "+ Add item" button.
      Now wait until a message about successful check-in appears and the barcode field gets wiped out for the next item.
      Expected response time: Less than a second (or even faster).
      Actual response time: More than 2 seconds, see attached screenshot.

      If you enter the next item's barcode without waiting it gets wiped out. The "+ Add item" button and the enter key are disabled during wait time.

      Check-in of 10 items currently takes more than 20 seconds, it should be less than 10 seconds (or even faster).

        TestRail: Results

          Attachments

            Issue Links

            is blocked by

            Bug - A problem which impairs or prevents the functions of the product. CIRC-144 Check-in of an item takes more than 2 seconds

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. UICHKIN-18 Checkin takes > 1 min with ~2.5 million records

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UICHKIN-57 Check In Takes 5.8 Seconds

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. UICHKOUT-69 Check-out takes more than 2 seconds per item

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-112 do not block GET requests that participate in the check-in operation (possible partial solution for UICHKIN-111)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                julianladisch Julian Ladisch
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases