Skip to content

[Due for payment 2026-10-22] Workspace chat is auto selected in participant list after removing distance expense from report #89862

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.3.68-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #87087
Email or phone of affected tester (no customers): josdjnosdjionjsdonjisod@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create a distance expense.
  4. Open the expense.
  5. Click Report > Remove from report.
  6. Go to self DM.
  7. Open the distance expense.
  8. Click on the header > Submit it to someone.

Expected Result:

Workspace chat will not be auto selected in participant list.

Actual Result:

Workspace chat is auto selected in participant list after removing distance expense from report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7146633_1778111443945.11.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. mhawryluk commented on May 11, 2026

    @mhawryluk
    Member

    created a fix PR (as a follow-up to the Consistent checkboxes and radio buttons UI
    one): #90165

  2. melvin-bot commented on May 12, 2026

    @melvin-bot

    Triggered auto assignment to @Beamanator, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  3. changed the title [-]Workspace chat is auto selected in participant list after removing distance expense from report[/-] [+][Due for payment 2026-05-20] Workspace chat is auto selected in participant list after removing distance expense from report[/+] on May 13, 2026
  4. melvin-bot commented on May 13, 2026

    @melvin-bot

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

  5. melvin-bot commented on May 13, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.73-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 2026-05-20. 🎊

  6. 22 remaining items

  7. Ollyws commented on Oct 22, 2026

    @Ollyws
    Contributor

    @Beamanator Seems like I never got paid here for my review of #90165, can we re-open? Thanks!

  8. changed the title [-]Workspace chat is auto selected in participant list after removing distance expense from report[/-] [+][Due for payment 2026-10-22] Workspace chat is auto selected in participant list after removing distance expense from report[/+] on Oct 22, 2026
  9. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  10. mallenexpensify commented on Oct 26, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @Ollyws due $250 via NewDot

  11. mallenexpensify commented on Oct 26, 2026

    @mallenexpensify
    Contributor

    @Ollyws plz complete the Contributor+ checklist and tag me in a post once you have. Thx

  12. Ollyws commented on Oct 26, 2026

    @Ollyws
    Contributor

    Contributor+ Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: N/A this was a followup to Consistent checkboxes and radio buttons UI #87087 which was a new feature.
      Link to the comment on the Issue:

    • [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.

    Regression Test Proposal Template. Needed for all bugs AND new features

    Regression Test Proposal

    Precondition:

    Test:

    1. Go to workspace chat.
    2. Create a distance expense.
    3. Open the expense.
    4. Click Report > Remove from report.
    5. Go to self DM.
    6. Open the distance expense.
    7. Click on the header > Submit it to someone.
    8. Verify the old report is not automatically selected.
    

    Do we agree 👍 or 👎

  13. Ollyws commented on Oct 26, 2026

    @Ollyws
    Contributor

    @mallenexpensify checklist done and payment requested.

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 productionDailyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions