[HOLD for payment 2024-08-29] [$250] Error while task creation via QAB when assigning task to yourself

[IuliiaHerets]

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.0.22-5
Reproducible in staging?: Y
Reproducible in production?: N
Issue was found when executing this PR: #47138
Email or phone of affected tester (no customers): applausetester+ck57@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Navigate to staging.new.expensify.com
2. Create a new workspace
3. Go to the Admins room
4. Tap + icon in composer >> select Assign task >> Enter task title/description
5. Assignee the task to yourself (assign to me option)
6. Tap green FAB button
7. Click on the Quick Action button and complete the task assignment flow.

Expected Result:

Task should be successfully created via QAB when assign task to yourself

Actual Result:

Error when assigning task to yourself via QAB.
"Hidden" is displayed instead of user's email for already created tasks

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

Bug6576715_1724126159179.Recording__142.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~015871a3b0adb66304
• Upwork Job ID: 1825794705774448587
• Last Price Increase: 2024-08-20
• Automatic offers:
• allgandalf | Reviewer | 103599149
• nkdengineer | Contributor | 103599150

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @VictoriaExpensify

[melvin-bot]

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

[melvin-bot]

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

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

[IuliiaHerets]

We think that this bug might be related to #vip-vsb

[nkdengineer]

Proposal

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

Error when assigning task to yourself via QAB.
"Hidden" is displayed instead of user's email for already created tasks

What is the root cause of that problem?

We always pass isCurrentUser param as false here

App/src/libs/actions/Task.ts

Line 837 in 80236f5

setAssigneeValue(accountLogin, accountID, reportID, chatReport, false, skipConfirmation);

then because the chat report is undefined, an optimistic chat report is generated for the current user then assigneeChatReportID in the param of CreateTask API become invalid reportID which causes the error

App/src/libs/actions/Task.ts

Line 796 in 80236f5

setAssigneeChatReport({

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

We should pass isCurrentUser as accountID === currentUserAccountID or I think we can remove isCurrentUser and use assigneeAccountID to check the assignee is the current user or not

setAssigneeValue(accountLogin, accountID, reportID, chatReport, accountID === currentUserAccountID, skipConfirmation);

App/src/libs/actions/Task.ts

Line 837 in 80236f5

setAssigneeValue(accountLogin, accountID, reportID, chatReport, false, skipConfirmation);

What alternative solutions did you explore? (Optional)

NA

[techievivek]

Hmm, I am unable to figure out any recent change that could have caused this but this is not reproducible on prod. 😕