Rules - Categorize message from Concierge disappears after applying rule to existing expense

[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: 9.3.31-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: #83005
Email or phone of affected tester (no customers): soindjoidjionjiosjn@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:

Precondition:

• Enable Rules in More features.

1. Go to staging.new.expensify.com
2. Create an expense with Cat as merchant without category in workspace chat.
3. Make sure categorize message from Concierge appear in the report.
4. Go to workspace settings > Rules.
   5.  Click Add merchant rule.
5. Create a merchant rule that changes merchant to Dog when merchant is Cat.
6. Open the created rule.
7. Enable Apply to existing unsubmitted expenses > Save rule.
8. Open the expense from Step 2.

Expected Result:

Categorize message from Concierge will not disappear after applying rule to existing unsubmitted expenses.

Actual Result:

Categorize message from Concierge disappears after applying rule to existing unsubmitted expenses.

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: #83005

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

[luacmartins]

Hmm I think this might be expected? That message was trying to auto-categorize the expense, but since the rule did that, the message serves no purpose. @JmillsExpensify wdyt?