Error when assigning a user who already has a vacation delegate as your own delegate

[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.1.71-9
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #64869
Email or phone of affected tester (no customers): +12795553311
Issue reported by: Applause Internal Team
Device used: Web, mWeb, Andoid, iOS
App Component: Other

Action Performed:

1. Log in to staging.new.expensify.com with Account A
2. Navigate to Settings > Profile > Status
3. Add any random account as a vacation delegate
4. Log in with Account B
5. Navigate to Settings > Profile > Status
6. Add Account A as a vacation delegate

Expected Result:

Status page with selected delegate should be displayed. No errors expected if valid email.

Actual Result:

Error message is displayed: "There was an error updating your vacation delegate."

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 @carlosmiceli (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @sonialiap (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]

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

[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.

[rushatgabhane]

this is expected. we cannot assign a user who is on a vacation

[carlosmiceli]

@rushatgabhane should this be closed then?

[rushatgabhane]

yes we can