[Due for payment 2026-01-16] [Due for payment 2026-01-15] Reports - Violation does not show up on expense row when additional attendee is not added

[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: 9.2.95-0
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 BrowserStack: #78315
Email or phone of affected tester (no customers): shduhsdbiushdisuhdsiu@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Search

Action Performed:

Preconditions:

• Rules are enabled.
• Enable Attendee tracking in Rules.
• Make Advertising category require attendees in category settings.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense with any category except Advertising. Do not add additional attendee.
4. Open expense report.
5. Change category to Advertising.
6. Go to Reports > Expenses.
7. Go to Reports > Reports.

Expected Result:

"Multiple attendees required for this category" violation will show up on expense row because additional attendee is not added.

Actual Result:

"Multiple attendees required for this category" violation does not show up on expense row when additional attendee is not added.

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: @RachCHopkins

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #78315

[melvin-bot]

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

[melvin-bot]

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

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