Details
-
Bug
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
Core: F - Sprint 86, Core: F - Sprint 87
-
5
-
Prokopovych
Description
Steps to repro:
- Log into bugfest environment
- Create a request
- Select a requester who is a proxy for another user (you can use cboerema)
- In the popup, indicate that you want to request on behalf of sponsor
- Save request
Expected: The sponsor should display as the requester and the patron initially entered (cboerema) should display below as the proxy. Request should not save on its own and, when it is saved, it should continue to display the the sponsor as the requester.
Actual: Everything looks good for a second on the create form but then the request saves automatically and it saves incorrectly (cboerema is listed as the requester)
Additional info:
- c.awenius tested this as part of bugfest on March 25 and it was working at that time. What could have happened to cause it to later fail?
- We did make a minor change to the display of this data on the create form during Q1 2020 (
UIREQ-413) and I remember testing it myself. I would be surprised if I missed this at that time, but maybe I did? - Okay, I just tested this in edelweiss and the same thing happened there! https://folio-edelweiss.dev.folio.org/ Looks like the test case for this was pretty weak so testers didn't notice it was failing. I just updated the test case to make it more clear.
TestRail: Results
Attachments
Issue Links
- relates to
-
UIREQ-413 Proxy and requester switched on the request create form
-
- Closed
-
-
UIREQ-454 Request as proxy: Save button doesn't work the first time you click it
-
- Closed
-
-
UIREQ-455 Request as proxy: Default pickup service point not populating for sponsor
-
- Closed
-
-
UIREQ-456 Request as proxy: Error duplicating a proxy request
-
- Closed
-
-
SUP-9 CLONE - Get error when trying to check out as proxy
-
- Closed
-
-
UICHKOUT-614 Get error when trying to check out as proxy
-
- Closed
-