Requests
(UXPROD-790)
|
|
| Status: | Closed |
| Project: | mod-circulation |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 23.5.3 | Parent: | Requests |
| Type: | Bug | Priority: | P2 |
| Reporter: | Stephanie Buck | Assignee: | Alexander Kurash |
| Resolution: | Done | Votes: | 0 |
| Labels: | bugfest_R1.2023 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | EPAM-Veg Sprint 161, EPAM-Veg Sprint 162 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Development Team: | Vega | ||||||||||||||||||||
| Release: | Orchid (R1 2023) Bug Fix | ||||||||||||||||||||
| Epic Link: | Requests | ||||||||||||||||||||
| RCA Group: | Implementation coding issue | ||||||||||||||||||||
| Affected releases: |
Orchid (R1 2023)
|
||||||||||||||||||||
| Description |
|
Overview: In some circumstances FOLIO returns an error for recalls. This can be reproduced using the steps below, but the steps can probably be simplified. These are not edge cases but rather very common scenarios. I have not involved In transit and other statuses, but would not be surprised if the error would appear also when they are part of the scenario. Steps to Reproduce: (Items awaiting pickup and checked out)
Expected Results: To get a success banner for the recall request in step 9. A red banner "this request was not placed successfully" / http 500 internal server error Additional Information: It is possible to place hold requests at step 9, but not recall requests. As holds are always allowed with TLR and the request is placed through the discovery system EDS, it will become a hold and trigger a successful message to the patron. However, the loan period will not be as expected when there is a mix of recall and hold requests at the same instance, so it's not a acceptable outcome. Steps to Reproduce: (paged and checked out)
Expected Results: To get a success banner for the recall request in step 7 Actual Results: a red banner ”this request was not placed successfully” / http 500 internal server error Additional Information: |
| Comments |
| Comment by Stephanie Buck [ 20/Mar/23 ] |
|
Discovered while testing other TLR test cases. There is no current test case for this. |
| Comment by Haykanush Markosyan [ 24/Mar/23 ] |
|
Both scenarios are tested in snapshot environment. Attached you can find the recordings => C380488.mp4
|
| Comment by JenkinsNotifications [ 28/Mar/23 ] |
|
Deployed to Orchid bf env. Moved status to In bugfix review from status Awaiting deployment. Please proceed with verification |
| Comment by Haykanush Markosyan [ 29/Mar/23 ] |
|
I have retested both scenarios in bugfest environment. Works as expected. Attached you can find the recordings: CIRC-1759_retest1.mp4
|
| Comment by Oleksandr Hrusha [ 29/Mar/23 ] |
|
Hello Stephanie Buck, could you please confirm fix on bugfest env? |