Skip to content

Workspace - Workspace chat member list does not remove user when user has left the chat #40417

Closed

Description

@izarutskaya

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.63-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create a new workspace.
  3. Go to workspace chat.
  4. Mention User B.
  5. Invite User B from the whisper.
  6. Send a message to the workspace chat.
  7. As User B, go to workspace chat.
  8. As User B, leave the workspace chat.
  9. As User A, click on the chat header > Members.

Expected Result:

User B will be removed from the workspace chat member list.

Actual Result:

User B is not removed from the workspace chat member list, even though User B has left the workspace chat.

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

Bug6453287_1713425268442.left_workspace_member_list.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019627df30080310e8
  • Upwork Job ID: 1783472042234789888
  • Last Price Increase: 2024-04-25

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 18, 2024
  2. melvin-bot commented on Apr 18, 2024

    @melvin-bot

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

  3. melvin-bot commented on Apr 18, 2024

    @melvin-bot

    Triggered auto assignment to @isabelastisser (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. github-actions commented on Apr 18, 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.
  5. izarutskaya commented on Apr 18, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #collect project.

  6. NikkiWines commented on Apr 18, 2024

    @NikkiWines
    Contributor

    I think this is a deploy blocker so re-adding the label

  7. 18 remaining items

  8. melvin-bot commented on Apr 25, 2024

    @melvin-bot
  9. melvin-bot commented on Apr 25, 2024

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @ikevin127 (Internal)

  10. rezkiy37 commented on Apr 26, 2024

    @rezkiy37
    Contributor

    Hey!
    I just wanted to let you know about my vacation for next week. I will be back on 06.05.2024. Meanwhile, I asked @waterim to help with this issue.
    See you soon!

  11. MonilBhavsar commented on Apr 26, 2024

    @MonilBhavsar
    Contributor

    PR is in review

  12. ikevin127 commented on Apr 26, 2024

    @ikevin127
    Contributor

    Will I be needed for review here ? 🙂

  13. MonilBhavsar commented on Apr 26, 2024

    @MonilBhavsar
    Contributor

    Issue is on server side and hence the PR. So not really, thank you though!

  14. melvin-bot commented on May 3, 2024

    @melvin-bot

    @isabelastisser, @MonilBhavsar, @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  15. isabelastisser commented on May 3, 2024

    @isabelastisser
    Contributor

    Hey,@ikevin12, can you please provide an update? Thanks!

  16. ikevin127 commented on May 3, 2024

    @ikevin127
    Contributor

    @isabelastisser I was told in #40417 (comment) that my help as a reviewer is not needed here since this is a server side issue and PR which I don't have access to review.

  17. isabelastisser commented on May 3, 2024

    @isabelastisser
    Contributor

    My bad, @MonilBhavsar, is there an update? Thanks!

  18. MonilBhavsar commented on May 6, 2024

    @MonilBhavsar
    Contributor

    PR was deployed last week.
    We can close this out after creating regression test.

  19. MonilBhavsar commented on May 6, 2024

    @MonilBhavsar
    Contributor

    Regression test issue created https://github.com/Expensify/Expensify/issues/393485
    ... and closing

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.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions