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-01-07] [$250] Expense-"moved this expense" does not disappear when report is deleted offline & return online #76625
Version Number: 9.2.71-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:#71220 Email or phone of affected tester (no customers):sdjoinsdjodsnjdosijnio@gmail.com Issue reported by: Applause Internal Team Device used: Mac 26.1 / Chrome App Component: Other
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Open the expense report.
Click Report field > Create report.
Go offline.
Click More > Delete to delete the empty report.
Open the new report with the moved expense.
Click on the report link.
BUG 1: User can access the deleted report offline by accessing the link in the system message.
10.Go back to the new report.
Go online.
BUG 2: "moved this expense" message does not disappear (it will disappear if we perform Step 1 to 8 directly without involving offline mode).
Expected Result:
BUG 1: "moved this expense" message will disappear because the old report is deleted.
BUG 2: "moved this expense" message wil disappear (it will disappear if we perform Step 1 to 8 directly without involving offline mode).
Actual Result:
BUG 1: User can access the deleted report offline by accessing the link in the system message.
BUG 2: "moved this expense" message does not disappear (it will disappear if we perform Step 1 to 8 directly without involving offline mode).
👋 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 [-][$250] Expense-"moved this expense" does not disappear when report is deleted offline & return online[/-][+][Due for payment 2026-01-07] [$250] Expense-"moved this expense" does not disappear when report is deleted offline & return online[/+]on Dec 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@truph01@mallenexpensify 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]
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Go to workspace chat.
Create an expense.
Open the expense report.
Click Report field > Create report.
Go offline.
Click More > Delete to delete the empty report.
Open the new report with the moved expense.
Verify that: the system message at 50% opacity with strikethrough (unclickable)
Activity
melvin-bot commentedon Dec 3, 2025
Triggered auto assignment to @mallenexpensify (
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 Dec 3, 2025
Triggered auto assignment to @inimaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 3, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 3, 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:
inimaga commentedon Dec 3, 2025
Investigating...
inimaga commentedon Dec 3, 2025
Cause of this issue/regression seems to be this pr. Testing a revert.
inimaga commentedon Dec 3, 2025
Okay, a clean revert isn't straight forward. And seems easier to fix the root cause issue. Incoming PR.
49 remaining items
[-][$250] Expense-"moved this expense" does not disappear when report is deleted offline & return online[/-][+][Due for payment 2026-01-07] [$250] Expense-"moved this expense" does not disappear when report is deleted offline & return online[/+]melvin-bot commentedon Dec 31, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 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-01-07. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 31, 2025
@truph01 @mallenexpensify 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]
truph01 commentedon Jan 5, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-da3c-a08e-db72-5e896a516294melvin-bot commentedon Jan 9, 2026
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
mallenexpensify commentedon Jan 10, 2026
Payment Summary
Contributor: @ paid $250 via Upwork
Contributor+: @truph01 due $250 via NewDot
^ Test case created
JmillsExpensify commentedon Apr 5, 2026
$250 approved for @truph01