Skip to content

[Due for payment 2025-06-16] [Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report #63505

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.59-0
Reproducible in staging?: Yes
Reproducible in production?: No
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): sdjonsjdosdjodi@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses to the workspace chat.
  4. Click on the expense preview.
  5. Select all expenses via checkbox.
  6. Click on the report header subtitle to return to workspace chat.
  7. On workspace chat, click + > Create report.
  8. Submit two more expenses to the new report.
  9. Click on the new report from Step 7.

Expected Result:

Selection mode will not persist in the new report.

Actual Result:

Selection mode from the other report persists in the new 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

Bug6851040_1749077887678.20250605_065228.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @greg-schroeder

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

    @melvin-bot

    Triggered auto assignment to @greg-schroeder (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 Jun 4, 2025

    @melvin-bot

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

  4. github-actions commented on Jun 4, 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.
  5. melvin-bot commented on Jun 4, 2025

    @melvin-bot

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

  6. BlameGPT commented on Jun 5, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

  7. MonilBhavsar commented on Jun 5, 2025

    @MonilBhavsar
    Contributor
  8. 22 remaining items

  9. changed the title [-][Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-] [+][Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+] on Jun 6, 2025
  10. melvin-bot commented on Jun 6, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.60-2-staging 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-13. 🎊

    For reference, here are some details about the assignees on this issue:

  11. melvin-bot commented on Jun 6, 2025

    @melvin-bot

    @DylanDylann @greg-schroeder @DylanDylann 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]

  12. changed the title [-][Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-] [+][Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+] on Jun 9, 2025
  13. melvin-bot commented on Jun 9, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.61-0 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-16. 🎊

    For reference, here are some details about the assignees on this issue:

  14. melvin-bot commented on Jun 9, 2025

    @melvin-bot

    @DylanDylann @greg-schroeder @DylanDylann 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]

  15. changed the title [-][Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-] [+][Due for payment 2025-06-16] [Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+] on Jun 9, 2025
  16. melvin-bot commented on Jun 9, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.62-0 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-16. 🎊

    For reference, here are some details about the assignees on this issue:

  17. melvin-bot commented on Jun 9, 2025

    @melvin-bot

    @DylanDylann @greg-schroeder @DylanDylann 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