[$250] Attendees - Selected attendee is cleared after creating Scan/Distance/Per diem expense

[vincdargento]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.23-2
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Distance.
4. Enter waypoints > Next.
5. On confirmation page, click Show more.
6. Note that Attendees field has yourself selected.
7. Create the expense.
8. Go to transaction thread.

Expected Result:

Attendees field in the transaction thread will retain the selection on the confirmation page.

Actual Result:

Attendees field in the transaction thread is cleared.

This issue happens with Scan, Distance and Per diem expense.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021907932172983504516
• Upwork Job ID: 1907932172983504516
• Last Price Increase: 2025-04-03

Issue Owner

Current Issue Owner: @allroundexperts

[melvin-bot]

Triggered auto assignment to @lschurr (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 @marcaaron (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[vincdargento]

@lschurr FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[francoisl]

We're CP'ing a PR to hide the attendee selector, I'm going to remove the blocker label and keep this open as an issue to fix later.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021907932172983504516

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.24-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging][Fix]: Disable attendee option #59633

If no regressions arise, payment will be issued on 2025-04-16. 🎊

For reference, here are some details about the assignees on this issue:

• @allroundexperts requires payment through NewDot Manual Requests
• @alitoshmatov requires payment through NewDot Manual Requests

[melvin-bot]

@allroundexperts / @alitoshmatov @lschurr @allroundexperts / @alitoshmatov The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

### Payment Summary
Upwork Job
- Reviewer: @allroundexperts owed $250 via NewDot
- Reviewer: @alitoshmatov owed $250 via NewDot

BugZero Checklist (@lschurr)

• I have verified the correct assignees and roles are listed above and updated the necessary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1907932172983504516/hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[lschurr]

Just confirming, the PR linked was only actioned by @fedirjh and @francoisl

That means no payment is due to the others tagged in this GH right? @alitoshmatov @alitoshmatov

[alitoshmatov]

Right

[lschurr]

Corrected payment summary:

• Contributor: $250 @fedirjh (please request via NewDot)

[allroundexperts]

@lschurr This is actually not completed yet. We're still fixing this in a follow up PR.

[lschurr]

Alright, reopening.

[allroundexperts]

#60067 is fixing this.

[melvin-bot]

@allroundexperts Huh... This is 4 days overdue. Who can take care of this?