Repository navigation
[$1000] Closed accounts aren't removed from workspace members list #20264
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
- Invite new user (that doesn't have a NewDot account)
- Valifdate this user, then login with this new user account in ND in private mode
- Close this new user account
- Switch to Desktop App with admin account and check members list
Expected Result:
- Closed account was removed from the members list
Actual Result:
- Closed accounts are still displayed in the members list
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
Version Number: 1.3.24.4
Reproducible in staging?: Yes
Reproducible in production?: No
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
Notes/Photos/Videos: Any additional supporting documentation
Closed account
Bug6081613_ws-member-closed-account.mp4
Member's list
Bug6081613_ws-members-list.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~0190db70a7a3eb2f5b
- Upwork Job ID: 1672152459568193536
- Last Price Increase: 2023-06-30
Activity
OSBotify commentedon Jun 6, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Jun 6, 2023
Triggered auto assignment to @Julesssss (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.Beamanator commentedon Jun 6, 2023
Hopinggggg this isn't due to my PR: https://github.com/Expensify/Web-Expensify/pull/37723
@Julesssss let me know if you want help investigating
Julesssss commentedon Jun 6, 2023
Regardless it doesn't seem like a blocker. Testing locally now.
Julesssss commentedon Jun 6, 2023
It seems very weird that this only occurs on Desktop staging:
@Beamanator I doubt your changes would lead to this Desktop only issue, right?
Beamanator commentedon Jun 6, 2023
Ooh ya I have no idea how mu changes would only cause this on desktop....
roryabraham commentedon Jun 6, 2023
I think the problem is that desktop deploys are broke
60 remaining items
melvin-bot commentedon Jul 4, 2023
@twisterdotcom @Julesssss @muttmuure @aimane-chnaif this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks!
melvin-bot commentedon Jul 4, 2023
Current assignee @aimane-chnaif is eligible for the Internal assigner, not assigning anyone new.
twisterdotcom commentedon Jul 4, 2023
I disagree. Just because something is rare, does not mean we shouldn't fix it. Ideally, every case is polished, edge or not. If we think this does need to be
Internalthen we should make it that, and prioritise it accordingly. That sounds like what we'll do.If you agree @Julesssss, let's just leave you assigned and make it a
Monthly?Julesssss commentedon Jul 5, 2023
Sure, but it's probably going to just sit in my backlog for the rest of the year tbh.
mvtglobally commentedon Jul 6, 2023
Issue not reproducible during KI retests. (First week)
twisterdotcom commentedon Aug 7, 2023
If this is not reproducible, can we close?