Open malafry opened 5 months ago
Multiple bug like behaviours. A Spike ticket is necessary to define what we are trying to address.
I have fixed the 'Invalid Parameter redirect_uri' issue. It was a misconfiguration in keycloak where the wildcard had been left out of the production URL. Common misconception that this is not allowed in production - at the end of the address it is. What is not allowed is having a wildcare in the domain i.e https://nrpti-f00029..test/etc
Describe the Bug User has poor success rate in attaching documents to a new record, accompanied by spinning wheel, login error, and access restriction pop-ups. They reliably get a spinning wheel when attaching documents to new records through browse and drag and drop; they are occasionally required to sign in again when navigating the website; and documents are attached with different success rates over time (i.e., very frequent fail rate, but not guaranteed to duplicate bug).
Expected Behaviour When adding new Dam Safety Inspection records to NRPTI in Production, and when uploading a document to the record using drag and drop, the document should appear below the drag and drop box without a spinning wheel or requiring a window refresh:
When the user then clicks "Save Record", the record should publish with all provided information and documents.
Actual Behaviour When adding new Dam Safety Inspection records to NRPTI in Production, and when uploading a document to the record using drag and drop, a spinning wheel appears that doesn't resolve over time. When the user refreshes the window, the following screen appears ("Login Error: Invalid parameter: redirect_uri"):
When the user logs back in, the record is created but the document isn't attached. When the user tries to edit the record and update it with the attached document, the spinning wheel appears again and the process repeats. Eventually there is a successful upload.
Notes: 1) The spinning wheel and logged out problem is not a new behaviour. The user has had this problem in the past; however, when they log back in the record is created and the documents were attached successfully. The reason the bug issue is more pressing now is because the documents aren't attaching frequently after the timeout issue. 2) User occasionally gets the following screen as well:
3) User can have colleagues assist who don't seem to have the problem. However, I can verify that I occasionally have the login error and access restriction screen when refreshing on NRPTI, and I need to start back with the URL to the NRPTI main page. I haven't encountered the endless spinning wheel however.
Implications The user cannot reliably upload records with attached documents. In the interim, colleagues can attach documents for the user, but the user's account and privileges should allow them to do their assigned work.
Steps To Reproduce Steps to reproduce the behaviour:
Acceptance Criteria
-[ ] Create separate bug tickets if required