Skip to content

Expense - After submitting expense to WS chat, submitting expense to user submits to WS chat #62913

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.53-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: Exp
Email or phone of affected tester (no customers): applausetester+sjdoidj12@applause.expensifail.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. Create a workspace.
  3. Go to workspace chat.
  4. Submit an expense to workspace chat.
  5. Open FAB > Create expense > Manual.
  6. Enter amount > Next.
  7. On confirmation page, click To field.
  8. Select a user.
  9. Submit the expense.

Expected Result:

The expense will be submitted to the selected user.

Actual Result:

The expense is submitted to the workspace chat.

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

Bug6844214_1748409916864.20250528_132315.mp4

View all open jobs on GitHub

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

    @melvin-bot

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

  3. melvin-bot commented on May 28, 2025

    @melvin-bot

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

  4. github-actions commented on May 28, 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. robertjchen commented on May 28, 2025

    @robertjchen
    Contributor

    Looking for related PR

  6. BlameGPT commented on May 28, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

    Please 👍 or 👎

  7. removed
    DeployBlockerIndicates it should block deploying the API
    on May 28, 2025
  8. IuliiaHerets commented on May 28, 2025

    @IuliiaHerets

    Issue is not repro Win 11 / Chrome, v9.1.53-3

    bandicam.2025-05-28.20-56-07-094.mp4
  9. Beamanator commented on May 28, 2025

    @Beamanator
    Contributor

    Nice! Fixed!

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions