Report - Strikethrough system message navigate to the deleted report page

[lanitochka17]

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.2.89-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78101
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 pro /Chrome
App Component: Chat Report View

Action Performed:

1. Navigate to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Open the expense report.
5. Click Report field > Create report.
6. Go offline.
7. Click More > Delete to delete the empty report.
8. Open the new report with the moved expense.
9. Copy the the system message at 50% opacity with strikethrough and paste in the composer then send
10. Navigate to the link

Expected Result:

The copied system message shouldn't navigate to the deleted report page

Actual Result:

The system message shouldn't be clickable and navigate to the deleted report page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7039421_1767117356581.bandicam_2025-12-30_20-38-34-952.mp4

View all open jobs on GitHub

[melvin-bot]

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

[daledah]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The system message shouldn't be clickable and navigate to the deleted report page

What is the root cause of that problem?

with the deleted system message, when the user copy message we still setClipboardMessage with the full html

so when the user paste the message, it'll have the link to navigate to the deleted report page

App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx

Lines 864 to 866 in b37c2c7

	} else if (isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.MOVED_TRANSACTION)) {
	setClipboardMessage(getMovedTransactionMessage(reportAction));
	} else if (isMovedAction(reportAction)) {

App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx

Lines 754 to 756 in b37c2c7

	} else if (isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.UNREPORTED_TRANSACTION)) {
	setClipboardMessage(getUnreportedTransactionMessage(reportAction));
	} else if (isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.MARKED_REIMBURSED)) {

What changes do you think we should make in order to solve the problem?

if it's the pending delete system message, we should setClipboardMessage with the text after parsering the html to text

  else if (isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.UNREPORTED_TRANSACTION)) {
          ... 
          setClipboardMessage(isPendingDelete ? Parser.htmlToText(getUnreportedTransactionMessage(reportAction)) : getUnreportedTransactionMessage(reportAction));
  }

  else if (isActionOfType(reportAction, CONST.REPORT.ACTIONS.TYPE.MOVED_TRANSACTION)) {
          ... 
          setClipboardMessage(isPendingDelete ? Parser.htmlToText(getMovedTransactionMessage(reportAction)) : getMovedTransactionMessage(reportAction));
  }

with the isPendingDelete like we did here and here

App/src/pages/home/report/PureReportActionItem.tsx

Line 1351 in b37c2c7

const isPendingDelete = fromReport?.pendingFields?.preview === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE;

App/src/pages/home/report/PureReportActionItem.tsx

Line 1317 in b37c2c7

const isPendingDelete = fromReport?.pendingFields?.preview === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE;

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[mallenexpensify]

Tiny bug and wasn't really able to reproduce (also, I can't see anyone ever taking the steps in the OP)
Closing