[$250] Expense - Attendee row appears after merging from Reports when disabled in Rules

[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.3.24-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-5897/folder/13176708/41236908/1203274341
#71244
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

1. Launch app
2. Create workpace and enable rules
3. Create another workspace and enable rules
4. Create a manual expense in both workspace
5. Open a expense
6. Tap more - merge
7. Select the expense and second option in all section and continue
8. Note in confirmation page, "attendee" row is not shown
9. Go to reports - expense
10. Long press & select same expense (step 5) and merge selecting second option in all section and continue
11. Note in confirmation page, "attendee" row is shown
12. Go to inbox
13. Open workspace chat and open same expense used in step 5
14. Tap more - merge selecting expense & second option in all section and continue
15. Note in confirmation page, "attendee" row is shown

Expected Result:

When Attendees section is disabled in Rules:
Attendee row should NOT be displayed across all merge entry points [Expense screen
/ Reports list (long press) ].

Behavior must be consistent regardless of navigation path.

Actual Result:

Initial merge from workspace, attendee row is not shown correctly.
When merge from report, attendee row appears incorrectly.
After that, workspace merge also shows attendee row incorrectly.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mananjadhav

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022025645682814877857
• Upwork Job ID: 2025645682814877857
• Last Price Increase: 2026-02-22

[melvin-bot]

@youssef-lr recently merged #71244, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @greg-schroeder (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.

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