-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workspace - Workspace chat member list does not remove user when user has left the chat #40417
Comments
Triggered auto assignment to @NikkiWines ( |
Triggered auto assignment to @isabelastisser ( |
👋 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:
|
We think this issue might be related to the #collect project. |
I think this is a deploy blocker so re-adding the label |
Current assignee @NikkiWines is eligible for the DeployBlockerCash assigner, not assigning anyone new. |
👋 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:
|
Possibly tied to #35671 cc: @MonilBhavsar @rezkiy37 |
@thienlnam since you're app deployer today, what're your thoughts? Looks like is an bug / edge-case not covered by a new feature. Not sure if we want to block the deploy on this given this functionality didn't exist previously so it's not really breaking existing features. Maybe this can instead be patched as a follow up? |
Yeah I agree, this doesn't look like it needs to be a blocker |
Cool, removing the label then and dropping priority |
From a brief look, this looks like backend issue to me |
Hey! High-priority tasks currently occupy me. |
re-assigning to @MonilBhavsar per our discussion as he has context 🙇 |
Looking into this now |
Job added to Upwork: https://www.upwork.com/jobs/~019627df30080310e8 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @ikevin127 ( |
Hey! |
PR is in review |
Will I be needed for review here ? 🙂 |
Issue is on server side and hence the PR. So not really, thank you though! |
@isabelastisser, @MonilBhavsar, @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Hey,@ikevin12, can you please provide an update? Thanks! |
@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. |
My bad, @MonilBhavsar, is there an update? Thanks! |
PR was deployed last week. |
Regression test issue created https://github.com/Expensify/Expensify/issues/393485 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] 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:
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?
Screenshots/Videos
Bug6453287_1713425268442.left_workspace_member_list.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: