Skip to content

No confirmation message when create money expense via concierge chat #74206

Closed

Description

@nlemma

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: v9.2.44-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1739/folder/22315296/56014375/992049368
Email or phone of affected tester (no customers): fasdfasdf@fsfjfjsd.com
Issue reported by: Applause Internal Team
Device used: Lenovo 80ES / Windows 10 Pro
App Component: Chat Report View

Action Performed:

  1. Navigate to NewDot
  2. Create a fresh test account (email without "+", select manage my team's expense and QBD)
  3. Navigate to Concierge DM
  4. Send a message “Add an expense for $45 at Home Depot.”
  5. When green dot appears on workspace chat open the expense details page
  6. Verify there is an error at category field
  7. Add category from suggestions
  8. Go to Concierge

Expected Result:

Concierge should replies with a confirmation message

Actual Result:

Concierge does not replies with a confirmation message

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

Bug6993745_1762261813866.Recording__6581.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 4, 2025
  2. melvin-bot commented on Nov 4, 2025

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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 Nov 5, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 5, 2025

    @melvin-bot

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

  5. github-actions commented on Nov 5, 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. nlemma commented on Nov 5, 2025

    @nlemma
    Author

    @stephanieelliott I added the DeployBlokerCash label because the issue is not reproducible on prod on the current deploy.

  7. luacmartins commented on Nov 5, 2025

    @luacmartins
    Contributor

    I'm not sure that I understand the OP. Additionally, the behavior in staging is the same as production. So I'll demote this.

  8. added and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 5, 2025
  9. puneetlath commented on Nov 5, 2025

    @puneetlath
    Contributor

    Closing after discussion here. This was human error.

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions