[HOLD for payment 2024-08-27] [$250] Expense - Copied content from report title system message is different from the system message

[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: 9.0.17-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers):
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat
3. Submit an expense
4. Go to expense report
5. Click on the report header
6. Click Title
7. Edit the title and save it
8. Refresh the page
9. Right click on the report title system message > Copy to clipboard
10. Paste the content in the composer

Expected Result:

The copied content will be the same as the system message

Actual Result:

The copied content is different from the system message

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6563216_1722938498447.bandicam_2024-08-06_17-57-15-872.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~018e6a5a151d252557
• Upwork Job ID: 1820881503609119225
• Last Price Increase: 2024-08-06
• Automatic offers:
• DylanDylann | Reviewer | 103505015

Issue Owner

Current Issue Owner: @DylanDylann

[melvin-bot]

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

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

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[cristipaval]

This is the offending PR, but I wouldn't consider this a blocker TBH.

[abdulrahuman5196]

This is the offending PR, but I wouldn't consider this a blocker TBH.

I doubt if this is a regression from that particular PR. Because it only changed the usage with a common component. cc: @neonbhai What is your thoughts?

[roryabraham]

agreed in slack that this is NAB