Skip to content

Task - Chat header turns to skeleton after assigning task to user with no chat history #42273

Closed

Description

@m-natarajan

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.74-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: exp around https://expensify.testrail.io/index.php?/tests/view/4561795&group_by=cases:section_id&group_id=291936&group_order=asc
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:

  1. Go to staging.new.expensify.com and login
  2. Go to FAB > Assign task.
  3. Assign a task to a user that has no chat history.

Expected Result:

After the task is created, the chat header will not show skeleton.

Actual Result:

After the task is created, the chat header shows skeleton.

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

Bug6482493_1715848404484.20240516_163050.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @aldo-expensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on May 16, 2024
  2. melvin-bot commented on May 16, 2024

    @melvin-bot

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

  3. melvin-bot commented on May 16, 2024

    @melvin-bot

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

  4. melvin-bot commented on May 16, 2024

    @melvin-bot

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:

    1. If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
      • If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
    2. Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
      • You can adjust the urgency of the issue to better represent the gravity of the bug.
      • If the issue is super low priority, feel free to un-assign yourself.
      • Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
      • If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.

    Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.

  5. github-actions commented on May 16, 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.
  6. 73 remaining items

  7. aldo-expensify commented on Jul 23, 2024

    @aldo-expensify
    Contributor

    Thanks @kavimuru . I'll have to investigate and see what else may be the issue.

  8. kadiealexander commented on Aug 1, 2024

    @kadiealexander
    Contributor

    @aldo-expensify any updates here?

  9. aldo-expensify commented on Aug 1, 2024

    @aldo-expensify
    Contributor

    no, I haven't investigated again, I'll do it asap

  10. kadiealexander commented on Aug 12, 2024

    @kadiealexander
    Contributor

    Not overdue

  11. aldo-expensify commented on Aug 20, 2024

    @aldo-expensify
    Contributor

    Investigating now....

  12. aldo-expensify commented on Aug 20, 2024

    @aldo-expensify
    Contributor

    Hmm I don't see "Assign task" anymore in the menu, so I can't reproduce with the existing steps... Should we close?

    If you create a task from within a chat, then the "Assign task" action appears in the FAB (big green button) menu, but it appears with a pre-selected assignee, so we can't either reproduce this way.

    image
  13. aldo-expensify commented on Aug 23, 2024

    @aldo-expensify
    Contributor

    I'll close this since I think it is no longer reproducible. Feel free to reopen if you find new steps to reproduce.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions