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-02-03] Expense - Member's expense is moved to self workspace chat after moving it to new report #80400
Version Number: 9.3.8-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:#76000 Email or phone of affected tester (no customers):#76000 Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Create a workspace and invite a member and non-admin approver to the workspace.
Go to staging.new.expensify.com
[Member] Create an expense in workspace chat.
[Non-admin approver] Open the expense report > Click More > Submit.
[Non-admin approver] Open member and your workspace chat.
→ The expense appears in both member and your workspace chat.
[Member] Open your workspace chat.
→ The expense does not appear in member workspace chat.
[Non-admin approver] Go to Account > Troubleshoot > Clear cache and restart > Reset and refresh OR relogin.
[Non-admin approver] Go back to member workspace chat and your workspace chat.
→ The expense disappears from member's workspace chat and it remains in your workspace chat.
Expected Result:
When non-admin approver moves member's expense to a new report, the expense will be moved to member's workspace chat in a new report.
Actual Result:
When non-admin approver moves member's expense to a new report, the expense initially appears in both member and approver's workspace chat (Step 5).
After reset app or relogin, the moved expense only appears in approver's workspace chat.
👋 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: #76000 - "Allow admin to create report on behalf of employee" by @s77rt (High confidence) Related Issues: #75607
Recommendation: REVERT
PR #76000 introduced a new feature allowing admins to create reports on behalf of employees, but it has a critical synchronization bug. When a non-admin approver moves a members expense to a new report, the expense initially appears in both the member's and approver's workspace chat. After cache clear/relogin, the expense only remains in the approver's workspace chat, which is incorrect.
The PR was merged on 2026-01-23 at 00:52:58 UTC, and this issue was reported ~23 hours later. The timing and affected functionality match perfectly.
Labels: Keeping DeployBlockerCash (this blocks the App deploy). This is a frontend bug requiring changes to App code.
Not in Production: Issue notes this is a new feature that doesn't exist in production
Verification
PR #76000 modified these key files related to the bug:
src/libs/actions/Report.ts - Changed to use ownerPersonalDetails instead of creatorPersonalDetails when building new report optimistic data
src/pages/Search/SearchTransactionsChangeReport.tsx - Modified to determine and pass the target owner's personal details
src/pages/iou/request/step/IOURequestStepReport.tsx - Added logic to determine owner account ID from IOU actions
src/pages/iou/request/step/IOURequestEditReport.tsx - Updated to use owner personal details
The changes allow admins to create reports on behalf of employees by passing the employee's ownerPersonalDetails when calling createNewReport(). This causes the report to be associated with the employee's workspace chat via getPolicyExpenseChat(ownerAccountID, policyID).
Root Cause
When a non-admin approver moves a member's expense to a new report:
The frontend optimistically creates a new report with the member as the owner (using targetOwnerPersonalDetails)
The report is associated with the member's workspace chat via getPolicyExpenseChat()
However, there appears to be a mismatch between the optimistic frontend state and the backend response
The expense initially shows in both workspace chats due to optimistic update inconsistencies
After cache clear, only the backend state persists, showing the expense in the approver's chat instead of the member's
The bug suggests that either:
The optimistic data is incorrectly placing the expense in multiple workspace chats, OR
The backend is not respecting the ownerEmail parameter added in CreateAppReportParams, OR
There's a race condition in how the parent report ID is being set for the moved transaction
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.9-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann@dylanexpensify 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 23, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #76000
melvin-bot commentedon Jan 23, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 23, 2026
Triggered auto assignment to @dylanexpensify (
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 23, 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 23, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #76000 - "Allow admin to create report on behalf of employee" by @s77rt (High confidence)
Related Issues: #75607
Recommendation: REVERT
PR #76000 introduced a new feature allowing admins to create reports on behalf of employees, but it has a critical synchronization bug. When a non-admin approver moves a members expense to a new report, the expense initially appears in both the member's and approver's workspace chat. After cache clear/relogin, the expense only remains in the approver's workspace chat, which is incorrect.
The PR was merged on 2026-01-23 at 00:52:58 UTC, and this issue was reported ~23 hours later. The timing and affected functionality match perfectly.
Labels: Keeping
DeployBlockerCash(this blocks the App deploy). This is a frontend bug requiring changes to App code.Detailed Analysis
Evidence
Verification
PR #76000 modified these key files related to the bug:
src/libs/actions/Report.ts- Changed to useownerPersonalDetailsinstead ofcreatorPersonalDetailswhen building new report optimistic datasrc/pages/Search/SearchTransactionsChangeReport.tsx- Modified to determine and pass the target owner's personal detailssrc/pages/iou/request/step/IOURequestStepReport.tsx- Added logic to determine owner account ID from IOU actionssrc/pages/iou/request/step/IOURequestEditReport.tsx- Updated to use owner personal detailsThe changes allow admins to create reports on behalf of employees by passing the employee's
ownerPersonalDetailswhen callingcreateNewReport(). This causes the report to be associated with the employee's workspace chat viagetPolicyExpenseChat(ownerAccountID, policyID).Root Cause
When a non-admin approver moves a member's expense to a new report:
targetOwnerPersonalDetails)getPolicyExpenseChat()The bug suggests that either:
ownerEmailparameter added inCreateAppReportParams, ORs77rt commentedon Jan 24, 2026
non-admins should not even see the option to create reports on employees expense chats. It seems I overlooked that
13 remaining items
melvin-bot commentedon Jan 27, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 27, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.9-2 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-02-03. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 27, 2026
@DylanDylann @dylanexpensify 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]
melvin-bot commentedon Feb 3, 2026
Payment Summary
Upwork Job
BugZero Checklist (@dylanexpensify)
dylanexpensify commentedon Feb 5, 2026
dylanexpensify commentedon Feb 5, 2026
@DylanDylann please complete checklist
DylanDylann commentedon Feb 5, 2026
I think we don't require a checklist and payment here. This is a regression