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 2025-04-28] Expense - Expense is created in report from other workspace when a new workspace is selected #60234
Version Number: 9.1.28-1 Reproducible in staging?: Yes Reproducible in production?: Unable to check, new feature If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):sdjsdmiojoms@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Create two new workspaces.
Click FAB > Create expense > Manual.
Enter amount > Next.
Enter merchant and click Create expense.
Click FAB > Create expense > Manual.
Enter amount > Next.
Click Show more.
Click Report.
Click on the same report.
Click To field.
Select the second workspace.
Note that the Report field shows the new report title and not the one selected in Step 10.
Enter merchant.
Click Create expense.
Expected Result:
The expense should be created in a new report in the second workspace.
Actual Result:
The expense is created in the selected report from the first workspace in Step 10, even though another workspace is selected and Report field shows a new report in Step 13.
👋 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.
changed the title [-]Expense - Expense is created in report from other workspace when a new workspace is selected[/-][+][Due for payment 2025-04-28] Expense - Expense is created in report from other workspace when a new workspace is selected[/+]on Apr 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.30-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@luacmartins / @techievivek@CortneyOfstad@waterim 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 Apr 15, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 15, 2025
Triggered auto assignment to @CortneyOfstad (
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 Apr 15, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 15, 2025
👋 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:
rayane-d commentedon Apr 15, 2025
Discussing in https://expensify.slack.com/archives/C01GTK53T8Q/p1744712146580769
luacmartins commentedon Apr 15, 2025
We'll put this button behind a beta and tackle the issue as a follow up.
1 remaining item
luacmartins commentedon Apr 15, 2025
No longer available in staging. Demoting.
melvin-bot commentedon Apr 21, 2025
@waterim Eep! 4 days overdue now. Issues have feelings too...
[-]Expense - Expense is created in report from other workspace when a new workspace is selected[/-][+][Due for payment 2025-04-28] Expense - Expense is created in report from other workspace when a new workspace is selected[/+]melvin-bot commentedon Apr 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.30-4 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 2025-04-28. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 21, 2025
@luacmartins / @techievivek @CortneyOfstad @waterim 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]
luacmartins commentedon Apr 22, 2025
We can close this issue since it's fixed.