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-06-11] [Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM #62763
Version Number: 9.1.51-0 Reproducible in staging?: Yes Reproducible in production?: Unable to check, new feature 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):applausetester+jsidosjdno@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Windows 11 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Log in with Expensifail account.
Go to staging.new.expensify.com
Go to workspace chat.
Submit two expenses.
Click + > Create report.
Click on the report preview with expenses.
Select two expenses via checkbox.
Click More > Move expenses.
Select the new empty report from Step 4.
Click More > Delete.
Delete the report.
Go to self DM.
Click on one of the expenses.
Right click on "moved this expense to" message > Reply in thread.
Expected Result:
The system message for moving expense will be complete.
Actual Result:
The system message for moving expense is incomplete. It shows "moved this expense to".
When the message is opened in thread, it shows "moved this expense to Inaccessible 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.
changed the title [-]Expense - Incomplete system message after moving expense's report and moving it to self DM[/-][+][Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM[/+]on Jun 2, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.54-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@allgandalf@NicMendonca@allgandalf 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]
changed the title [-][Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM[/-][+][Due for payment 2025-06-11] [Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM[/+]on Jun 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.58-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@allgandalf@NicMendonca@allgandalf 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 May 26, 2025
Triggered auto assignment to @NicMendonca (
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 May 26, 2025
Triggered auto assignment to @MonilBhavsar (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 26, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 26, 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:
BlameGPT commentedon May 26, 2025
Possible culprit PRs for this issue
Please 👍 or 👎
actual: #58020
MonilBhavsar commentedon May 26, 2025
Commented on the offending PR
12 remaining items
[-]Expense - Incomplete system message after moving expense's report and moving it to self DM[/-][+][Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM[/+]melvin-bot commentedon Jun 2, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 2, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.54-7 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-06-09. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 2, 2025
@allgandalf @NicMendonca @allgandalf 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]
allgandalf commentedon Jun 3, 2025
No checklist, this was a follow up issue, good to close
[-][Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM[/-][+][Due for payment 2025-06-11] [Due for payment 2025-06-09] Expense - Incomplete system message after moving expense's report and moving it to self DM[/+]melvin-bot commentedon Jun 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.58-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-06-11. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 4, 2025
@allgandalf @NicMendonca @allgandalf 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]