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
[Due for payment 2026-01-27] Expense - Invited member cannot see Attendee field #79710
Version Number: 9.3.3-0 Reproducible in staging?: Yes Reproducible in production?: No 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):sdjsjdoisnjdoisjosdj22@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Money Requests
👋 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) Related Issues: None identified
Recommendation: REVERT
PR #79050 introduced a regression where the Attendee field visibility is incorrectly tied to edit permissions. Users invited to "chat only" (not workspace members) cannot see the Attendee field because they lack edit permissions, even though they should be able to view it as read-only.
Labels: No changes needed - DeployBlockerCash is correctly applied for this Frontend bug.
📋 Detailed Analysis
Evidence
PR #79050 added the ability to require attendees based on category selection. The PR modified MoneyRequestView.tsx and added logic that ties the attendees field interactivity to the canEdit permission (line 1058: interactive={canEdit}).
Verification
The issue affects the attendees field in src/components/ReportActionItem/MoneyRequestView.tsx:
Lines 1041-1065: The attendees field uses interactive={canEdit} and shouldShowRightIcon={canEdit}
Line 324: canEdit is calculated based on whether the user is the expense creator, admin, or manager
When a user is invited to "chat only", they are not a workspace member, so canEdit = false
The MenuItemWithTopDescription component with interactive={false} makes the field appear disabled/hidden
Root Cause
The PR incorrectly assumed that attendee field visibility should be controlled by edit permissions. However, the expected behavior is:
Workspace members with edit rights: Can edit the attendee field
Invited chat-only users: Should see the attendee field as read-only, but cannot edit it
The regression is that interactive={canEdit} prevents chat-only users from seeing the field at all, when they should see it in a non-interactive (read-only) state.
Comparison
In MoneyRequestConfirmationListFooter.tsx (lines 737-758), the attendees field correctly uses isReadOnly instead of canEdit, which is the pattern that should have been followed in MoneyRequestView.tsx.
changed the title [-]Expense - Invited member cannot see Attendee field[/-][+][Due for payment 2026-01-27] Expense - Invited member cannot see Attendee field[/+]on Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@JS00001@brianlee-expensify 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]
Activity
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
melvin-bot commentedon Jan 15, 2026
Triggered auto assignment to @brianlee-expensify (
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 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:
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)
Related Issues: None identified
Recommendation: REVERT
PR #79050 introduced a regression where the Attendee field visibility is incorrectly tied to edit permissions. Users invited to "chat only" (not workspace members) cannot see the Attendee field because they lack edit permissions, even though they should be able to view it as read-only.
Labels: No changes needed -
DeployBlockerCashis correctly applied for this Frontend bug.📋 Detailed Analysis
Evidence
PR #79050 added the ability to require attendees based on category selection. The PR modified
MoneyRequestView.tsxand added logic that ties the attendees field interactivity to thecanEditpermission (line 1058:interactive={canEdit}).Verification
The issue affects the attendees field in
src/components/ReportActionItem/MoneyRequestView.tsx:interactive={canEdit}andshouldShowRightIcon={canEdit}canEditis calculated based on whether the user is the expense creator, admin, or managercanEdit = falseMenuItemWithTopDescriptioncomponent withinteractive={false}makes the field appear disabled/hiddenRoot Cause
The PR incorrectly assumed that attendee field visibility should be controlled by edit permissions. However, the expected behavior is:
The regression is that
interactive={canEdit}prevents chat-only users from seeing the field at all, when they should see it in a non-interactive (read-only) state.Comparison
In
MoneyRequestConfirmationListFooter.tsx(lines 737-758), the attendees field correctly usesisReadOnlyinstead ofcanEdit, which is the pattern that should have been followed inMoneyRequestView.tsx.JS00001 commentedon Jan 15, 2026
Going to CP a fix here to disable the feature: #79620
ikevin127 commentedon Jan 15, 2026
🗒️ Noted for follow-up PR.
5 remaining items
test: add debug logs for Expensify#79710
IuliiaHerets commentedon Jan 16, 2026
Chrome / 9.3.3-2
Not reproduce anymore by QA team
Screen.Recording.2026-01-16.at.10.42.29.mp4
JS00001 commentedon Jan 16, 2026
CP'd a fix to hide this feature, closing. @ikevin127 Lets fix this in a follow up
[-]Expense - Invited member cannot see Attendee field[/-][+][Due for payment 2026-01-27] Expense - Invited member cannot see Attendee field[/+]melvin-bot commentedon Jan 20, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-01-27. 🎊
melvin-bot commentedon Jan 20, 2026
@JS00001 @brianlee-expensify 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]