You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-10-17] Expenses-Distance expense is created in workspace chat instead of self DM #72155
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
Go to staging.new.expensify.com
Click FAB > Track distance
Select any start and stop point
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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:
@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]
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.
Activity
melvin-bot commentedon Oct 9, 2025
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.melvin-bot commentedon Oct 9, 2025
Triggered auto assignment to @MarioExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 9, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 9, 2025
👋 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:
c3024 commentedon Oct 9, 2025
This is a new feature and not on production. This need not be a deploy blocker IMO.
pecanoro commentedon Oct 9, 2025
I tested in classic and it's still working well so it's a problem with App. I am going to remove the
DeployBlockerlabel because of that.13 remaining items
chiragsalian commentedon Oct 9, 2025
Unassigning myself since an engineer was already assigned and is actively working on this.
MarioExpensify commentedon Oct 9, 2025
Fix is on its way here.
[-]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[/+]melvin-bot commentedon Oct 10, 2025
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:
melvin-bot commentedon Oct 10, 2025
@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]
melvin-bot commentedon Oct 17, 2025
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.