[EXTDAM-210] [S3] User sessions overlap when browsing assets Created: 11/Dec/20  Updated: 17/Jun/22  Resolved: 19/Jan/21

Status: Closed
Project: External DAMs
Component/s: s3
Affects Version/s: 1.0.3
Fix Version/s: 1.0.4

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Evzen Fochr
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File exampe-of-issue.mov     PNG File superuser-and-eric-diff-browsers.png    
Issue Links:
relation
is related to EXTDAM-193 [S3] Adapt UI tests to the new list view Closed
is related to EXTDAM-174 [170, 173] Implement view which is ab... Closed
is related to EXTDAM-190 [S3] Display the folder you are in Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: DAM Phase 2
Sprint: Add-Ons 55
Story Points: 2

 Description   

When you have two or more users trying to browse assets in s3 the sessions can overlap each other. Users might enter the app in a folder which is not at the top level.

Steps to reproduce

  1. User1, open the dam app and browse the assets.
  2.  In a separate browser login as a different user, say user2, open the dam app and observe that you are at the same folder as user1.
    See exampe-of-issue.mov

Notes
This issue seems to be caused by the change from tree view to list view (see EXTDAM-174)


Generated at Mon Feb 12 01:52:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.