Admin also appears in the "invite new members list in workspace

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. create new account
2. create new workspace
3. go to Settings > Workspace > Members
4. you can find yourself as member in list
5. click on invite button

Expected Result:

user should not appears in invite list ifr part of workspace

Actual Result:

user itself appears in invite list

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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.29-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
Notes/Photos/Videos: Any additional supporting documentation

Screen.Recording.2023-06-17.at.1.52.21.PM.mov

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686990342042729

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @zanyrenney (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

👋 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.

[melvin-bot]

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

[Julesssss]

@kavimuru is this only occurring on web, or was that the only platform tested? Also was this tested on production?

[Julesssss]

I'm not able to reproduce this... Can you @zanyrenney?

My user is not showing in search.
I am signed in as [email protected]

[Julesssss]

Reducing priority

[gadhiyamanan]

@Julesssss please try with new account

[Julesssss]

THis is a new account. I created the user, created the workspace, and immediately opened the member page. Anyway, I'll leave the issue open while we attempt to reproduce.

[gadhiyamanan]

THis is a new account. I created the user, created the workspace, and immediately opened the member page. Anyway, I'll leave the issue open while we attempt to reproduce.

@Julesssss if it is new account why it shows number of users in list

[Pujan92]

I am not able to reproduce in dev.

[hungvu193]

I'm also not able to reproduce

[Julesssss]

@Julesssss if it is new account why it shows number of users in list

The domain already existed in OldDot. I'm not sure how I can verifiy a new user on staging that isn't associated with an email I control.

[kavimuru]

@Julesssss I tested in public domain account.

[Julesssss]

Sorry, I meant did Applause test all of the platforms? Or just web? Also, was this tested on production or just staging? I'm asking because it helps us to determine whether it should be a blocker.

[kavimuru]

@Julesssss It is not reproducible in production. It is reproducible in all platforms in staging.

[Julesssss]

Ah thanks. We should update the checkboxes in that case

[Julesssss]

@zanyrenney are you able to reproduce this? So far only Applause can, so maybe this was fixed elsewhere?

[zanyrenney]

No, I am not able to reproduce either:

I am on staging v1.3.29-8 so this isn't correct:

It is reproducible in all platforms in staging.

[zanyrenney]

chatted with @Julesssss in DM to confirm, we should close this as its not happening anymore.