Dev Homepage - Download full Paper from Explore More Research opens an Access denied error #2884
Labels
P1: Launch blocker
Needs fixing before we launch, schedule some time to investigate & fix
Milestone
View your issue at Applause Testing Services - https://platform.applause.com/products/27563/testcycles/380123/issues/5719229
---- ACTION DETAILS ----
Action Performed:
Expected Result:
Download full Paper should contain related paper to download.
Actual Result:
Download full Paper opens an Access denied error.
Additional Info:
Error Code/Message:
---- Applause Team Lead Recommendation ----
From Katarzyna Wladyszewska
Reproducible: Yes
In scope: Yes
Not a duplicate: yes
Seems valid: yes
Suggested value: very valuable
Comment:
---- ENVIRONMENT ----
Language:English,Operating System:Windows,Operating System Version:7,Web Browser:Chrome,Operating System Major Version:Windows 7
2022-09-06 05:54:30.0:I uploaded wrong videos for the reported issues #5719224 and #5718229. The videos got switched. I uploaded the correct video
(Access-denied-error-Recording #591) now.
The other video Recording #590 actually belongs to the issue #5719224.
Thanks
2022-09-06 02:50:02.0:Hello Radhika,
I cannot see the error access denied. Could you check your video?
Thanks, Katarzyna
---- APPLAUSE PROPERTIES ----
Applause Issue/Bug ID: 5719229
Title: Dev Homepage - Download full Paper from Explore More Research opens an Access denied error
Status: Pending Approval
Type: Functional
Frequency: Every Time
Severity: High
Product (Build): Global Health (Global Health.Map)
Test Cycle: Global Health - Dev Test Cycle - 9/2/2022
---- 1 Community Reproductions ----
Katarzyna Wladyszewska on 2022-09-07 20:10:35.0
macOS - Monterey 12.X - Monterey 12.5.1 - English - Chrome
---- APPLAUSE ATTACHMENT(S) ----
Bug5719229_Access-denied-error-Recording__591.mp4 : https://utest-dl.s3.amazonaws.com/6414/27563/380123/5719229/bugAttachment/Bug5719229_Access-denied-error-Recording__591.mp4?AWSAccessKeyId=AKIAJ2UIWMJ2OMC3UCQQ&Expires=1978351572&Signature=sUFSESxcl%2B3DXACl4vBmCb0cA%2Bs%3D
The text was updated successfully, but these errors were encountered: