Rules - Rules behavior unchanged after merchant match type is changed to 'Exactly matches"

[jponikarchuk]

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.3.22-1
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: #82438
Email or phone of affected tester (no customers): applausetester+aqwa@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 13 / iOS 18.7.1, Samsung Galaxy A52 / Android 14, Windows 11 / Chrome
App Component: Workspace Settings

Action Performed:

Preconditions:

1. Prepare two accounts (Admin and Member)
2. As Admin create a workspace and invite the member to the workspace
3. Enable rules in more feature

Steps:

1. (Admin) navigate to rules in workspace setting, scroll down and add merchant rule:

• Match type: Contains
• Merchant: "Coffee"
• Category: "Meals & Entertainment"

2. (Admin) Save the rule
3. (Member) create expenses with merchants "Starbucks Coffee" → Verify rule applies
4. (Admin) Edit the "Coffee" rule created above
5. (Admin) Change Match type from "Contains" to "Exactly matches" and save the rule
6. (Member) create an expense with merchant: "Starbucks Coffee"

Expected Result:

After member created the second expense when the rule already changed, the rule should not be applied (no longer contains match). Also there should be system message displayed on the expense details.

Actual Result:

Rules remain active after the admin updates the merchant match type to “exactly matches". Also, there's no system message displayed to show whether the category is automatically set by concierge or by the workspace rules.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #82438

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @stephanieelliott (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.

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