Workspace - Details RHP switches to current user after transferring ownership

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.67-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76164
Email or phone of affected tester (no customers): htad26+qwqewegd@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition
User A is the workspace owner.
User B is a non-owner admin in User A’s workspace.

1. Sign in as User B.
2. Navigate to the Workspace tab.
3. Click the three-dot menu on User A’s workspace, where you are a non-owner admin.
4. Select Transfer ownership and complete the flow.
5. Sign in as User A and navigate to Workspace > Members.
6. Select User B, then click Transfer ownership.
7. Complete the transfer flow and observe the Details RHP.

Expected Result:

After transferring ownership, the details RHP should remain open on the selected user’s profile which is User B's profile (Production behavior)

Actual Result:

After transferring ownership, the details RHP switches to the user’s own profile(User A) instead of staying on the selected user’s details RHP (User B)

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @MonilBhavsar (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source