[$250] Attendees field is missing on the confirmation page when creating per diem expense from FAB

[mitarachim]

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: 9.1.40-1
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: #60067
Email or phone of affected tester (no customers): applausetester+khcategory19@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Workspace has imported per diem rates.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Per diem.
4. Select a destination.
5. Complete the rest of the flow and reach confirmation page.
6. Note that Attendees field is present on the confirmation page.
7. Close the RHP.
8. Open FAB > Create expense > Per diem.
9. Repeat Step 4 and 5 from FAB.

Expected Result:

Attendees field will be present on the confirmation page when create per diem expense flow is initiated from FAB.

Actual Result:

Attendees field is missing on the confirmation page when create per diem expense flow is initiated from FAB.

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

Bug6823266_1746540242601.20250506_220033.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021919809646032177414
• Upwork Job ID: 1919809646032177414
• Last Price Increase: 2025-05-06

Issue Owner

Current Issue Owner: @dominictb

[melvin-bot]

Triggered auto assignment to @slafortune (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 @JS00001 (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.