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-09-22] Expense - "Moved this expense to" without report number seen after merging track expense. #70338
Version Number: 9.2.9-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 TestRail:#68204 Email or phone of affected tester (no customers):ibellicotest+1769@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb) - Windows 11 / Chrome App Component: Money Requests
Action Performed:
Prerequisite: Account has at least two workspaces.
Prerequisite 2: Account has a Self DM.
Open the staging.new.expensify.com website.
Open any workspace chat.
Create a manual expense.
Return to "Inbox"
Create a new manual expense and submit it to Self DM.
Tap on "Submit to someone" below the expense.
Submit the expense to a workspace different than the used on step 2.
Navigate to workspace where track expense was submitted.
Open the report.
Tap on "More" and select "Merge"
Select the expense created on step 3 and tap on "Continue"
Select all the details of expense created on step 3 and finish the merging process.
When redirected to chat, navigate to the report of the remaining expense.
Note that two "Moved this expense to" messages are displayed, but one of them doesn´t show any report number.
Expected Result:
When merging a track expense, the "Moved this expense" message generated, should still show a report number.
Actual Result:
When merging a track expense, two "Moved this expense to" system messages are seen, but only the second one displays a report number in it.
👋 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.
@dominictb@youssef-lr, When expenses are merged multiple times, the previous toReportID may reference a deleted report, making it impossible to retrieve the report name for display here
changed the title [-]Expense - "Moved this expense to" without report number seen after merging track expense.[/-][+][Due for payment 2025-09-22] Expense - "Moved this expense to" without report number seen after merging track expense.[/+]on Sep 15, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.13-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@mollfpr@VictoriaExpensify 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 Sep 11, 2025
Triggered auto assignment to @VictoriaExpensify (
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 Sep 11, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Sep 11, 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:
melvin-bot commentedon Sep 11, 2025
💬 A slack conversation has been started in #expensify-open-source
francoisl commentedon Sep 11, 2025
cc @youssef-lr @hoangzinh
hoangzinh commentedon Sep 11, 2025
@dominictb @youssef-lr, When expenses are merged multiple times, the previous toReportID may reference a deleted report, making it impossible to retrieve the report name for display here
App/src/pages/home/report/PureReportActionItem.tsx
Lines 1153 to 1160 in 80b3440
I fixed it by rendering an empty row for those report actions in this commit. Let me know if it doesn't make sense to you guys.
1 remaining item
melvin-bot commentedon Sep 11, 2025
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.
melvin-bot commentedon Sep 11, 2025
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.
melvin-bot commentedon Sep 11, 2025
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.
[-]Expense - "Moved this expense to" without report number seen after merging track expense.[/-][+][Due for payment 2025-09-22] Expense - "Moved this expense to" without report number seen after merging track expense.[/+]melvin-bot commentedon Sep 15, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 15, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.13-1 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-09-22. 🎊
melvin-bot commentedon Sep 15, 2025
@mollfpr @VictoriaExpensify 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]