Skip to content

[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

Closed

Description

@jponikarchuk

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.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.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses.
  4. Click + > Create report.
  5. Click on the report preview with expenses.
  6. Select two expenses via checkbox.
  7. Click More > Move expenses.
  8. Select the new empty report from Step 4.
  9. Click More > Delete.
  10. Delete the report.
  11. Go to self DM.
  12. Click on one of the expenses.
  13. 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".

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

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

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

    @melvin-bot

    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.

  3. melvin-bot commented on May 26, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 26, 2025

    @melvin-bot

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

  5. github-actions commented on May 26, 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. BlameGPT commented on May 26, 2025

    @BlameGPT
    Contributor
  7. MonilBhavsar commented on May 26, 2025

    @MonilBhavsar
    Contributor

    Commented on the offending PR

  8. 12 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jun 2, 2025
  10. 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
  11. melvin-bot commented on Jun 2, 2025

    @melvin-bot

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

  12. melvin-bot commented on Jun 2, 2025

    @melvin-bot

    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:

    • @allgandalf requires payment (Needs manual offer from BZ)
  13. melvin-bot commented on Jun 2, 2025

    @melvin-bot

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

  14. allgandalf commented on Jun 3, 2025

    @allgandalf
    Contributor

    No checklist, this was a follow up issue, good to close

  15. 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
  16. melvin-bot commented on Jun 4, 2025

    @melvin-bot

    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:

    • @allgandalf requires payment (Needs manual offer from BZ)
  17. melvin-bot commented on Jun 4, 2025

    @melvin-bot

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

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.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions