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-07-22] Reports - Removed merchant persists in expense row after removing merchant #65975
Version Number: 9.1.80-0 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail:#64761 Email or phone of affected tester (no customers):sjdionsjdodisjois@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Go to staging.expensify.com
Open 1:1 DM
Submit an expense with merchant to the user
Go to Reports > Expenses
Click on the expense row
Click Merchant
Clear the merchant and save it
Expected Result:
The merchant on the expense row will also be removed
Actual Result:
The merchant on the expense row persists after removing merchant
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6885029_1752259917158.20250712_024948.mp4
👋 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.
feat: standardize pay button #65296: Overhauled TransactionItemRow (which renders each expense row) while standardising the Pay button, and this may block the component from re-rendering after a merchant is cleared.
changed the title [-]Reports - Removed merchant persists in expense row after removing merchant[/-][+][Due for payment 2025-07-22] Reports - Removed merchant persists in expense row after removing merchant[/+]on Jul 15, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.80-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Jul 11, 2025
Triggered auto assignment to @stitesExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 11, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 11, 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:
rushatgabhane commentedon Jul 11, 2025
@BlameGPT find the culprits
BlameGPT commentedon Jul 11, 2025
Sus PRs on the scene
If not above, check these
luacmartins commentedon Jul 15, 2025
This is fixed on staging
Screen.Recording.2025-07-14.at.7.50.29.PM.mov
[-]Reports - Removed merchant persists in expense row after removing merchant[/-][+][Due for payment 2025-07-22] Reports - Removed merchant persists in expense row after removing merchant[/+]melvin-bot commentedon Jul 15, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 15, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.80-8 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-07-22. 🎊