Skip to content

[$250] Expense - Expense is still displayed on report preview after being moved to a different one. #66832

Closed

Description

@mitarachim

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.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-134/folder/12015305/39317664/797465572
Email or phone of affected tester (no customers): ibellicotest+1376@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least two workspaces available.

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Navigate to a different workspace chat.
  5. Create a new report but don´t submit any expense to it.
  6. Return to the first workspace chat.
  7. Open the expense created on it.
  8. Tap on the report field and select the report created on the second workspace.
  9. Tap on the arrow on the top left corner.
  10. Note that you land on an empty report.
  11. Tap on the arrow on the top left corner again.
  12. Note that the moved expense, is still displayed on the empty report preview, despite not being part of it anymore.
  13. Note that "Submit" button now shows "0,00" as amount.

Expected Result:

Expense that was moved to a different report, should not be displayed anymore on the same report preview.

Actual Result:

Report preview still displays an expense that was moved to a different report. Also, after expense was moved, "Submit" button shows "0,00" as amount.

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

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.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-134/folder/12015305/39317664/797465572
Email or phone of affected tester (no customers): ibellicotest+1376@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least two workspaces available.

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Navigate to a different workspace chat.
  5. Create a new report but don´t submit any expense to it.
  6. Return to the first workspace chat.
  7. Open the expense created on it.
  8. Tap on the report field and select the report created on the second workspace.
  9. Tap on the arrow on the top left corner.
  10. Note that you land on an empty report.
  11. Tap on the arrow on the top left corner again.
  12. Note that the moved expense, is still displayed on the empty report preview, despite not being part of it anymore.
  13. Note that "Submit" button now shows "0,00" as amount.

Expected Result:

Expense that was moved to a different report, should not be displayed anymore on the same report preview.

Actual Result:

Report preview still displays an expense that was moved to a different report. Also, after expense was moved, "Submit" button shows "0,00" as amount.

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

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.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-134/folder/12015305/39317664/797465572
Email or phone of affected tester (no customers): ibellicotest+1376@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least two workspaces available.

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Navigate to a different workspace chat.
  5. Create a new report but don´t submit any expense to it.
  6. Return to the first workspace chat.
  7. Open the expense created on it.
  8. Tap on the report field and select the report created on the second workspace.
  9. Tap on the arrow on the top left corner.
  10. Note that you land on an empty report.
  11. Tap on the arrow on the top left corner again.
  12. Note that the moved expense, is still displayed on the empty report preview, despite not being part of it anymore.
  13. Note that "Submit" button now shows "0,00" as amount.

Expected Result:

Expense that was moved to a different report, should not be displayed anymore on the same report preview.

Actual Result:

Report preview still displays an expense that was moved to a different report. Also, after expense was moved, "Submit" button shows "0,00" as amount.

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

Bug6894772_1753146136277.Moved.mp4

View all open jobs on GitHub

View all open jobs on GitHub

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021947644451609891826
  • Upwork Job ID: 1947644451609891826
  • Last Price Increase: 2025-07-22
Issue OwnerCurrent Issue Owner: @eh2077

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 22, 2025
  2. github-actions commented on Jul 22, 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.
  3. melvin-bot commented on Jul 22, 2025

    @melvin-bot

    Triggered auto assignment to @garrettmknight (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.

  4. melvin-bot commented on Jul 22, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jul 22, 2025

    @melvin-bot

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

  6. 2 remaining items

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 22, 2025
  8. changed the title [-]Expense - Expense is still displayed on report preview after being moved to a different one.[/-] [+][$250] Expense - Expense is still displayed on report preview after being moved to a different one.[/+] on Jul 22, 2025
  9. melvin-bot commented on Jul 22, 2025

    @melvin-bot
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 22, 2025
  11. melvin-bot commented on Jul 22, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (External)

  12. Gonals commented on Jul 22, 2025

    @Gonals
    Contributor

    @BlameGPT find culprit PR

  13. BlameGPT commented on Jul 22, 2025

    @BlameGPT
    Contributor

    Sus PRs on the scene

    If not above, check these

  14. melvin-bot commented on Jul 22, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  15. Gonals commented on Jul 22, 2025

    @Gonals
    Contributor

    @TMisiukiewicz, will your PR fix this one too?

  16. cristipaval commented on Jul 22, 2025

    @cristipaval
    Contributor

    the PR is being deployed to staging right now. Let's test when it's live

  17. cristipaval commented on Jul 22, 2025

    @cristipaval
    Contributor

    Just tested on Android mWeb and I can confirm it is fixed after that fix

  18. removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions