Merchant rules - No duplicate warning when Merchant is the same with different match type

[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: 9.3.11-17
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: #80847
Email or phone of affected tester (no customers): sdjoisjnoinjosndjoisj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Rules are enabled.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Rules.
3. Click Add merchant rule.
4. Click Merchant in "For expenses with:" > enter Apple > click Save.
5. Click Merchant in "Apply these updates:" > enter Banana > click Save.
6. Click Add merchant rule.
7. Click Merchant in "For expenses with:" > enter Apple.
8. Click Match type > select Exactly matches > click Save.
9. Click Merchant in "Apply these updates:" > enter Banana > click Save.
10. Click Add merchant rule.

Expected Result:

Duplicate warning will show up because Merchant is the same as the existing rule.

Actual Result:

Duplicate warning does not show up when Merchant is the same as the existing rule with different match type.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7062459_1769822497622.8.mp4

View all open jobs on GitHub

[melvin-bot]

@luacmartins recently merged #80847, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @garrettmknight (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]

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

[melvin-bot]

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

[github-actions]

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