Skip to content

[HOLD for payment 2024-02-15] [$500] Task - Task assigned to "Hidden" does not show "Hidden" as assignee in main chat #34052

Closed

Description

@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.22-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:
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:

Issue found when executing PR #29730

Action Performed:

  1. Go to FAB > Assign task
  2. Enter title > Next
  3. Click Assignee
  4. Enter a valid email with no display name that is registered on ND but has no chat history with the user
    (use yonghongkok2+03011@gmail.com
    )
  5. Create the task

Expected Result:

The task preview in the main chat will show "Hidden" as the assignee

Actual Result:

The task preview in the main chat does not show "Hidden" as the assignee

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

Bug6333411_1704479061341.20240105_195946__1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01e3fabdb897c1d05d
  • Upwork Job ID: 1744829796306513920
  • Last Price Increase: 2024-01-16
  • Automatic offers:
    • hoangzinh | Contributor | 28116810
    • dukenv0307 | Contributor | 28117853
Issue OwnerCurrent Issue Owner: @stephanieelliott

Activity

  1. github-actions commented on Jan 5, 2024

    @github-actions
    Contributor

    👋 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.
  2. melvin-bot commented on Jan 5, 2024

    @melvin-bot

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

  3. unidev727 commented on Jan 5, 2024

    @unidev727
    Contributor

    Proposal

    from: @unicorndev-727

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

    Task - Task assigned to "Hidden" does not show "Hidden" as assignee in main chat

    What is the root cause of that problem?

    This is not deploy blocker, I think (I can't find relevant PR for this issue in Deploy checklist).
    The root cause is that we didn't use getDisplayNameForParticipant here.

    const taskAssignee = assigneeDisplayName || LocalePhoneNumber.formatPhoneNumber(assigneeLogin);

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

    We should use getDisplayNameForParticipant.

    const taskAssignee = ReportUtils.getDisplayNameForParticipant(taskAssigneeAccountID);
    

    What alternative solutions did you explore?

    N/A

  4. mvtglobally commented on Jan 7, 2024

    @mvtglobally

    Still repro on build 1.4.22-2

    Recording.898.mp4
  5. 46 remaining items

  6. changed the title [-][$500] Task - Task assigned to "Hidden" does not show "Hidden" as assignee in main chat[/-] [+][HOLD for payment 2024-02-15] [$500] Task - Task assigned to "Hidden" does not show "Hidden" as assignee in main chat[/+] on Feb 8, 2024
  7. melvin-bot commented on Feb 8, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  8. melvin-bot commented on Feb 8, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.38-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-02-15. 🎊

    For reference, here are some details about the assignees on this issue:

  9. melvin-bot commented on Feb 8, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@hoangzinh] The PR that introduced the bug has been identified. Link to the PR:
    • [@hoangzinh] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@hoangzinh] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@hoangzinh] Determine if we should create a regression test for this bug.
    • [@hoangzinh] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@stephanieelliott] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  10. melvin-bot commented on Feb 12, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  11. stephanieelliott commented on Feb 16, 2024

    @stephanieelliott
    Contributor

    ^^ was tested and found to be NAB!

  12. stephanieelliott commented on Feb 16, 2024

    @stephanieelliott
    Contributor

    Summarizing payment on this issue:

    Upwork job is here: https://www.upwork.com/jobs/~1737876297360310272"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions