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
Self DM is marked as selected in recipient list when submitting track distance from self DM #82515
Version Number: 9.3.19-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:#78354 Email or phone of affected tester (no customers):usdjoiusoidjnonsjsjdo@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:
Go to staging.new.expensify.com
Go to self DM.
Track a distance expense in self DM.
Click Submit it to someone.
Expected Result:
Self DM will not be marked as selected in recipient list.
Actual Result:
Self DM is marked as selected in recipient list when submitting track distance.
👋 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.
Activity
melvin-bot commentedon Feb 15, 2026
@JS00001 recently merged #78354, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Feb 15, 2026
Triggered auto assignment to @laurenreidexpensify (
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 Feb 15, 2026
Triggered auto assignment to @deetergp (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 15, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 15, 2026
👋 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:
melvin-bot commentedon Feb 15, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
mountiny commentedon Feb 15, 2026
Testing the revert #82524
melvin-bot commentedon Feb 16, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
IuliiaHerets commentedon Feb 16, 2026
@mountiny v9.3.19-1 PR:82524
Windows 11 / Chrome
not repro
self.dm.mp4
mountiny commentedon Feb 16, 2026
@dmkt9 We will revert so we can deploy soon, but please prepare v2
IuliiaHerets commentedon Feb 16, 2026
@mountiny Chrome / v9.3.19-3
Not repro
Screen.Recording.2026-02-16.at.13.18.14.mp4