Remaining Renewals Decrease When Manual Refresh Is Needed to Complete a Renewal Transaction
Bug #1803753 reported by
Courtney Brown
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
When a renewal transaction requires the screen to be refreshed in the 3.1.6 web client, it decreases the number of remaining renewals inaccurately. For Example, a patron with 2 renewals checked out an item with a original due date of 10/15 . On 10/27, staff renewed the item for the patron, which should have left the patron with 1 renewal remaining. However, while attempting to renew the item, the screen freezes and a refresh is needed to continue the renewal process. After refreshing the screen, staff are able to continue with the renewal process but notice that another renewal was used while the screen refreshed, leaving the patron with 0 renewal, instead of the expected 1 renewal.
tags: | added: webstaffclient |
tags: |
added: checkout circulation removed: webstaffclient |
tags: |
added: circ-checkout removed: checkout |
To post a comment you must log in.