Skip to content

[Due for payment 2026-01-07] [$250] Expense-"moved this expense" does not disappear when report is deleted offline & return online #76625

Closed

Description

@nlemma

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Open the expense report.
  5. Click Report field > Create report.
  6. Go offline.
  7. Click More > Delete to delete the empty report.
  8. Open the new report with the moved expense.
  9. 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.
  10. 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).

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7019699_1764775433783.3.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021998071583220355109
  • Upwork Job ID: 1998071583220355109
  • Last Price Increase: 2025-12-08
  • Automatic offers:
    • daledah | Contributor | 109862810
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 3, 2025
  2. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    Triggered auto assignment to @inimaga (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Dec 3, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. inimaga commented on Dec 3, 2025

    @inimaga
    Contributor

    Investigating...

  7. inimaga commented on Dec 3, 2025

    @inimaga
    Contributor

    Cause of this issue/regression seems to be this pr. Testing a revert.

  8. inimaga commented on Dec 3, 2025

    @inimaga
    Contributor

    Okay, a clean revert isn't straight forward. And seems easier to fix the root cause issue. Incoming PR.

  9. 49 remaining items

  10. 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
  11. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    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:

  13. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    @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]

  14. truph01 commented on Jan 5, 2026

    @truph01
    Contributor

    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:

    1. Go to workspace chat.
    2. Create an expense.
    3. Open the expense report.
    4. Click Report field > Create report.
    5. Go offline.
    6. Click More > Delete to delete the empty report.
    7. Open the new report with the moved expense.
    8. Verify that: the system message at 50% opacity with strikethrough (unclickable)

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-da3c-a08e-db72-5e896a516294
  15. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  16. mallenexpensify commented on Jan 10, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @ paid $250 via Upwork
    Contributor+: @truph01 due $250 via NewDot

    ^ Test case created

  17. JmillsExpensify commented on Apr 5, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @truph01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions