[$500] Unable to mark system message unread in one transaction view

[kbecciv]

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: 1.4.59-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

1. Set up a collect policy with workspace chats (if necessary. Instructions here: https://expensify.slack.com/archives/C01GTK53T8Q/p1710887185511369?thread_ts=1710886648.492359&cid=C01GTK53T8Q)
2. Go to staging.new.expensify.com
3. Go to workspace chat that has no unsettled requests.
4. Create a manual request.
5. Set the category on the request.
6. Right click the set the category to "<category>". message and select "Mark as unread".
7. Scroll up and click New messages button.
8. Send a message in the report.
9. Mark the second message as unread.
10. Mark the first message (Expensify) as unread.

Expected Result:

The system message is marked as unread

Actual Result:

The system message is not marked as unread

Workaround:

n/a

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

Bug6435569_1712063366945.20240402_210425.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01280f37ab9c88e291
• Upwork Job ID: 1775321731724582912
• Last Price Increase: 2024-04-17
• Automatic offers:
• paultsimura | Reviewer | 0
• nkdengineer | Contributor | 0

[melvin-bot]

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

[kbecciv]

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

[amyevans]

Asked in #qa for what this looks like on prod

[amyevans]

Production:

bandicam.2024-04-02.17-31-26-884.mp4

[amyevans]

Asked in Slack for some help here and here, not making a ton of progress diagnosing this one

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01280f37ab9c88e291