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 - Create report button shows wrong workspace, expense cannot be moved #80414
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):sdjoisdnjodinjsodjidsji1@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
Action Performed:
Precondition-
Admin has two workspaces - A and B.
Workspace A is default workspace.
Admin invites member to workspace B.
Go to staging.new.expensify.com
[Member] Go to the invited workspace chat.
[Member] Create an expense.
[Admin] Open member's expense report.
[Admin] Click Report > Create report.
Expected Result:
Create report button will show workspace B as the subtitle.
Actual Result:
Create report button shows workspace A as the subtitle. As a result, the expense cannot be moved to a new report.
👋 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.
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:
@chuckdries @heyjennahay 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]
Coming from this issue #84618, here we are passing selectedReport?.policyID. However, on the IOURequestEditReport page, where we are using IOURequestEditReportCommon, we are not passing the second param to usePolicyForMovingExpenses. Because of that, it shows the current workspace under "Create report", but the report actually gets created in the default workspace.
Activity
melvin-bot commentedon Jan 24, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78634
melvin-bot commentedon Jan 24, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 24, 2026
Triggered auto assignment to @heyjennahay (
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 24, 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:
situchan commentedon Jan 26, 2026
Seems related to #76000
9 remaining items
s77rt commentedon Jan 26, 2026
Thanks for handling this!
m-natarajan commentedon Jan 26, 2026
Not Repro, Chrome and Honor x6b/ Android 14, v9.3.8-3 (Waiting for validation result in iOS)
Video.mp4
Screen.Recording.2026-01-26.at.22.05.57.mp4
chuckdries commentedon Jan 26, 2026
Thanks! This logic won't be different across devices, we're good to close
[-]Expense - Create report button shows wrong workspace, expense cannot be moved[/-][+][Due for payment 2026-02-03] Expense - Create report button shows wrong workspace, expense cannot be moved[/+]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. 🎊
melvin-bot commentedon Jan 27, 2026
@chuckdries @heyjennahay 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 Apr 9, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
jayeshmangwani commentedon May 28, 2026
Coming from this issue #84618, here we are passing
selectedReport?.policyID. However, on theIOURequestEditReportpage, where we are usingIOURequestEditReportCommon, we are not passing the second param tousePolicyForMovingExpenses. Because of that, it shows the current workspace under "Create report", but the report actually gets created in the default workspace.App/src/pages/iou/request/step/IOURequestEditReport.tsx
Line 55 in 8a02afe