[Due for payment 2025-11-28] [RCA #74928] Expense - Thread header shows "workspace rules" link in HTML tags

[vincdargento]

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.2.60-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74928
Email or phone of affected tester (no customers): applausetester+181101kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Admin invites member to workspace.
• Workspace is set up with business bank account.
• Member has personal bank account.

1. Go to staging.new.expensify.com
2. [Member] Create an expense below $100 in workspace chat.
3. [Member] Click Submit.
4. [Admin] Click Approve.
5. [Admin & Member] Open the expense report.
6. [Admin & Member] Right click on "paid with bank account 1111 via workspace rules" system message > Reply in thread.

Expected Result:

Thread header will not show "workspace rules" link in HTML tags.

Actual Result:

Thread header shows "workspace rules" link in HTML tags.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @bfitzexpensify

[melvin-bot]

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

[whiletrace]

@mountiny @bfitzexpensify @vincdargento Hello I am the author of PR #74928 I have a fix and am just getting ready to start testing if someone can help with that so we could get this completed quickly?