You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Attendee - Multiple attendee violation only applicable for the owner of the WS #79721
Version Number: v9.3.3-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:#79050 Email or phone of affected tester (no customers):testpayment935@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Windows 11 pro /Chrome App Component: Money Requests
Action Performed:
Preconditions:
Rules are enabled.
Enable Attendee tracking in Rules.
Navigate to staging.new.expensify.com
Go to workspace chat.
Create expenses with Equipment category and change the WS attendee to other user (remove WS owner)
Go to Workspace Settings > Categories.
Open Equipment settings.
Click Require fields.
Enable Require attendees.
Navigate straight to Reports > Expenses without opening the report first.
Expected Result:
"Multiple attendees required for this category" violation is shown on the expense row.
Actual Result:
"Multiple attendees required for this category" violation is not shown on the expense row if the attendee is other than yourself
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #79050 - feat: add ability to require attendees based on category selection (rework) by @ikevin127 (High confidence)
Recommendation: REVERT
PR #79050 introduced a bug in the attendee violation logic for the Reports > Expenses view. The violation check uses the current logged-in user's details instead of the expense creator's details, causing incorrect validation when viewing expenses created by other users.
Labels: Will KEEP DeployBlockerCash (App PR caused the issue). DeployBlocker label is not present on this issue.
Evidence
The bug reproduces when:
A user (not the workspace owner) creates an expense
They select a category requiring attendees but only add one attendee (not themselves)
The workspace owner views Reports > Expenses
Expected: Multiple attendees required for this category violation shows
Actual: No violation shows
This matches the issue description: Multiple attendee violation only applicable for the owner of the WS
Root Cause
The violation logic in src/libs/AttendeeUtils.ts checks if there are attendees besides the expense creator. However, the code in src/components/SelectionListWithSections/Search/TransactionListItem.tsx line 164 passes the current viewers details instead of the creators details.
Affected file: src/components/SelectionListWithSections/Search/TransactionListItem.tsx line 164 Fix needed: Pass transactionItem.from instead of currentUserDetails to syncMissingAttendeesViolation
Activity
github-actions commentedon Jan 15, 2026
👋 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:
melvin-bot commentedon Jan 15, 2026
Triggered auto assignment to @kadiealexander (
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 commentedon Jan 15, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #79050
melvin-bot commentedon Jan 15, 2026
💬 A slack conversation has been started in #expensify-open-source
OSBotify commentedon Jan 15, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #79050 - feat: add ability to require attendees based on category selection (rework) by @ikevin127 (High confidence)
Recommendation: REVERT
PR #79050 introduced a bug in the attendee violation logic for the Reports > Expenses view. The violation check uses the current logged-in user's details instead of the expense creator's details, causing incorrect validation when viewing expenses created by other users.
Labels: Will KEEP DeployBlockerCash (App PR caused the issue). DeployBlocker label is not present on this issue.
Evidence
The bug reproduces when:
This matches the issue description: Multiple attendee violation only applicable for the owner of the WS
Root Cause
The violation logic in src/libs/AttendeeUtils.ts checks if there are attendees besides the expense creator. However, the code in src/components/SelectionListWithSections/Search/TransactionListItem.tsx line 164 passes the current viewers details instead of the creators details.
Affected file: src/components/SelectionListWithSections/Search/TransactionListItem.tsx line 164
Fix needed: Pass transactionItem.from instead of currentUserDetails to syncMissingAttendeesViolation
ikevin127 commentedon Jan 15, 2026
@JS00001 This should be fixed by the ☝️ CP.
🗒️ Noted for follow-up PR.
ikevin127 commentedon Jan 16, 2026
This one can be closed as a non-issue because ☝️ that's how the feature is expected to work based on issue OP:
@JS00001 Should be closed as NAB.
IuliiaHerets commentedon Jan 16, 2026
Unable to repro on Windows 11 / Chrome in v9.3.3-2
No Attendees in required fields, only Description
bandicam.2026-01-16.15-53-40-933.mp4
JS00001 commentedon Jan 16, 2026
CP'd a fix to hide this feature, closing. @ikevin127 Lets fix this in a follow up