[LOW] [Splits] Task - Task report avatar in LHN shows task assignee instead of task creator before opening it

[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: 1.4.15-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

Precondition: User A and B have no prior chat and they are on private domain

1. [User A] In 1:1 DM with User C. create a task and assign it to User B
2. [User B] Note the avatar of task report in LHN
3. [User B] Open the task report

Expected Result:

In Step 2, when User B receives the task, the task report avatar should display the avatar of task creator

Actual Result:

In Step 2, when User B receives the task, the task report avatar displays task assignee avatar (User B) instead of task creator avatar
The task report avatar only shows the correct avatar (task creator) after opening the task report in Step 3

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

Bug6323106_1703187095047.bandicam_2023-12-22_00-33-54-109.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01dd3b25a9441185ce
• Upwork Job ID: 1737965082987188224
• Last Price Increase: 2023-12-21

Issue Owner

Current Issue Owner: @roryabraham

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

[melvin-bot]

Triggered auto assignment to @roryabraham (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[roryabraham]

Weird

[roryabraham]

Well what I'm seeing is that in step 2, the ownerAccountID is user A and the mangagerAccountID on the report is user B. Now going to click on the report as user B and see what happens.

[roryabraham]

Clarification – I was looking at the task report, but there's also a chat report that's created between users A and B

[roryabraham]

So it looks like the chat report that's optimistically created when assigning the task has the wrong participantAccountIDs

[roryabraham]

Or rather, not just the one that's optimistically created, but the one that user B receives via Pusher

[roryabraham]

Before user B clicks on the report, the participantAccountIDs array just had the accountID of B, in this case [185]. But after user B clicks on the report, the participantAccountIDs array had just the accountID of B, in this case [186].

Furthermore, I don't see any code that optimistically generates the chat report in this case.

[roryabraham]

Edit: the chat report is optimistically generated here, and the participantAccountID array is correct for the person who created the report.

[roryabraham]

At this point, I'm pretty sure that this is a back-end issue, so I'm going to remove the deploy blocker label and check this off.