[HOLD for payment 2023-06-29][$1000] Error message "Can't remove admin" isn't shown when selecting workspace admins

[Beamanator]

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. go to settings -> workspaces
   2.Select one workspace
2. go to members
3. try on removing admin

Expected Result:

Error should show and you should be able to remove an admin

Actual Result:

Admin can almost be removed, then error message is thrown

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: main
Reproducible in staging?: N
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
Expensify/Expensify Issue URL:
Issue reported by: @ashimsharma10
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686829788221639

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b1012f509c1a5e12
• Upwork Job ID: 1670661235088379904
• Last Price Increase: 2023-06-19

[melvin-bot]

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

[dukenv0307]

This issue will be fixed by My proposal in another issue

[Pujan92]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Error message "Can't remove admin" isn't shown when selecting workspace admins

What is the root cause of that problem?

In the latest migration, it seems we are using accountID for the WorkspaceMembersPage component but for the validate method we are comparing accountID with the email and that is causing the issue.

App/src/pages/workspace/WorkspaceMembersPage.js

Lines 289 to 290 in d396430

	_.each(this.state.selectedEmployees, (member) => {
	if (member !== this.props.policy.owner && member !== this.props.session.email) {

What changes do you think we should make in order to solve the problem?

We need to update the condition to consider accountID instead of the email property and for showing an error also we need to use accountID instead of login field.

App/src/pages/workspace/WorkspaceMembersPage.js

Lines 371 to 376 in d396430

	{!_.isEmpty(this.state.errors[item.login]) && (
	<FormHelpMessage
	isError
	message={this.state.errors[item.login]}
	/>
	)}

Result

Screen.Recording.2023-06-15.at.6.07.38.PM.mov

[kadiealexander]

@sobitneupane could you please take a look at this issue and confirm if it's the same root cause/fix as #20719 as per @dukenv0307's comment here?

[sobitneupane]

Nope @kadiealexander. It's a different issue.

I have reviewed @Pujan92's proposal. It will solve this issue. We can go with @Pujan92's proposal to solve this issue.

[sobitneupane]

@kadiealexander I would like to take C+ role here if possible.

[kadiealexander]

Reproduced this on desktop app. @sobitneupane happy to assign you here, thanks for volunteering!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01b1012f509c1a5e12

[melvin-bot]

Current assignee @kadiealexander is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Current assignee @sobitneupane is eligible for the External assigner, not assigning anyone new.

[kadiealexander]

@sobitneupane don't forget to leave the bow and eyes emojis on your review post to assign an engineer!

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

Current assignee @sobitneupane is eligible for the External assigner, not assigning anyone new.

[kadiealexander]

@bfitzexpensify I'm going OOO til the 26th so just assigning someone to keep this moving. Happy to take it back next week!

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[luacmartins]

Thanks for the help!

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.30-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix: Error message "Can't remove admin" isn't shown when selecting workspace admins #21023

If no regressions arise, payment will be issued on 2023-06-29. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@sobitneupane] The PR that introduced the bug has been identified. Link to the PR:
• [@sobitneupane] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@sobitneupane] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@sobitneupane] Determine if we should create a regression test for this bug.
• [@sobitneupane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@bfitzexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[kadiealexander]

Thanks for keeping an eye on this @bfitzexpensify!

[kadiealexander]

Sent contracts to everybody. @sobitneupane please don't forget about the checklist!

[kadiealexander]

Paid @Pujan92 including a bonus as per this
Paid @ashimsharma10 their reporting bonus

Once the checklist is complete I'll issue C+ payment and we can close this 🎉

[sobitneupane]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@sobitneupane] The PR that introduced the bug has been identified. Link to the PR:

#20506

• [@sobitneupane] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

#20506 (comment)

• [@sobitneupane] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

We were making transition (login->accountID) through multiple PRs and few cases might have missed out.

• [@sobitneupane] Determine if we should create a regression test for this bug.

We have decided to disable the checkbox for admin recently. It is being worked on in another issue. So, error message is no longer needed.