[$250] Workspace - "Remove members" and "Make admin" options are present for owner

[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!

---

Issue found when validating #45732
Version Number: 9.0.15-4
Reproducible in staging?: y
Reproducible in production?: unable to check new feature
Issue reported by: applause internal team

Action Performed:

1. Launch New Expensify app.
2. Go to workspace settings > Members.
3. Long press on the owner.
4. Tap Select.
5. Tap on the dropdown.

Expected Result:

Owner should not be able to be selected (production behavior).

Actual Result:

Owner can be selected and there are "Remove members" and "Make members" options which are not applicable to the owner.

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0110a7f901ae8b6a28
• Upwork Job ID: 1818787780851878074
• Last Price Increase: 2024-07-31
• Automatic offers:
• neonbhai | Contributor | 103438189

Issue Owner

Current Issue Owner: @getusha

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[m-natarajan]

We think that this bug might be related to #wave-collect - Release 1