If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Have a chat with 2 users (User A, User B)
Have a few attachments posted by User B (Attachment 1, 2, 3)
Make User A press and open the latest attachment (Attachment 3)
Make User B delete Attachment 3
Expected result:
Nothing disruptive should happen to User A’s experience. They continue to see that attachment until they close the window
Actual result:
The whole attachment modal/carousel abruptly closes (even if they scrolled to another image)
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.10Reproducible in staging?: yReproducible in production?: yIf this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentationhttps://user-images.githubusercontent.com/43996225/236339219-067cdc95-1b40-4b29-9d3b-4da0cbbf4650.mov
Recording.492.mp4
Expensify/Expensify Issue URL: Issue reported by: @kidroca Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683212386358629
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Upwork Job URL: https://www.upwork.com/jobs/~01afedd756887cbd8d
Upwork Job ID: 1655921750675152896
Last Price Increase: 2023-05-09
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected result:
Nothing disruptive should happen to User A’s experience. They continue to see that attachment until they close the window
Actual result:
The whole attachment modal/carousel abruptly closes (even if they scrolled to another image)
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.10
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/236339219-067cdc95-1b40-4b29-9d3b-4da0cbbf4650.mov
Recording.492.mp4
Expensify/Expensify Issue URL:
Issue reported by: @kidroca
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683212386358629
View all open jobs on GitHub
Upwork Automation - Do Not Edit