Skip to content

[Due for payment 2025-10-17] Expenses-Distance expense is created in workspace chat instead of self DM #72155

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: v9.2.28-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #70240
Email or phone of affected tester (no customers): agexptest+pr0810.5@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome, Samsung S23FE/ Android 15, iPhone 13 Mini/ iOS 18.5
App Component: Money Requests

Action Performed:

Preconditions:
Create a new account with a Gmail address (pick "Track and budget expenses" in the intent selector).
Have one workspace.
Personal policy auto reporting is off + Group policy auto reporting is off

  1. Go to staging.new.expensify.com
  2. Click FAB > Track distance
  3. Select any start and stop point
  4. Create the expense

Expected Result:

The distance expense is created in the self DM.

Actual Result:

The distance expense is created in 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

Bug6969240_1759977349691.distance_expense.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 Oct 9, 2025
  2. melvin-bot commented on Oct 9, 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 Oct 9, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 9, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 9, 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. c3024 commented on Oct 9, 2025

    @c3024
    Contributor

    This is a new feature and not on production. This need not be a deploy blocker IMO.

  7. pecanoro commented on Oct 9, 2025

    @pecanoro
    Contributor

    I tested in classic and it's still working well so it's a problem with App. I am going to remove the DeployBlocker label because of that.

  8. 13 remaining items

  9. removed their assignment
    on Oct 9, 2025
  10. chiragsalian commented on Oct 9, 2025

    @chiragsalian
    Contributor

    Unassigning myself since an engineer was already assigned and is actively working on this.

  11. self-assigned this
    on Oct 9, 2025
  12. MarioExpensify commented on Oct 9, 2025

    @MarioExpensify
    Contributor

    Fix is on its way here.

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Oct 10, 2025
  14. changed the title [-]Expenses-Distance expense is created in workspace chat instead of self DM[/-] [+][Due for payment 2025-10-17] Expenses-Distance expense is created in workspace chat instead of self DM[/+] on Oct 10, 2025
  15. melvin-bot commented on Oct 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.28-5 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-10-17. 🎊

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

    • @s77rt does not require payment (Contractor)
  16. melvin-bot commented on Oct 10, 2025

    @melvin-bot

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

  17. melvin-bot commented on Oct 17, 2025

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions