Skip to content
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

[Bug]: Incorrect description for an accepted user invitation when the user is deleted #56918

Open
arunsathiya opened this issue Oct 9, 2021 · 0 comments

Comments

@arunsathiya
Copy link
Contributor

arunsathiya commented Oct 9, 2021

Quick summary

On a WordPress.com site, invite an user from https://wordpress.com/people/team and once they accept the account, delete their user account. Visit the invites area of the People tab, and click on the invitation you sent. See that the messaging reads The person will still remain a member of this site. but that's incorrect because the user was deleted/removed.

image

Steps to reproduce

  • Start at https://wordpress.com/people/team
  • Invite another WordPress.com user to the site.
  • Once they accept the invitation and join, delete their account.
  • Visit Invites area of the People tab.
  • Click on the invitation that you sent.
  • See that the messaging reads The person will still remain a member of this site. but it's incorrect.

What you expected to happen

If the user is deleted, that line must be removed. The rest of the messaging If you no longer wish to see this record, you can clear it. can remain though.

What actually happened

We see an incorrect message: The person will still remain a member of this site.

Context

Manual testing.

Browser

Mozilla Firefox

Simple/Atomic

Atomic

Other notes

  • I tested on Atomic for now. Yet to see if this happens on simple.
  • This occurs even when the deleted user has deleted their WordPress.com account altogether. (Well, to delete the WordPress.com account they first have to be removed from the site)

Reproducibility

Consistent

Severity

All

Available workarounds?

No response

Workaround details

Not applicable.

@arunsathiya arunsathiya added [Type] Bug Needs triage Ticket needs to be triaged labels Oct 9, 2021
@arunsathiya arunsathiya added this to Needs triage in HE Triaging Board (new bugs) via automation Oct 9, 2021
@Robertght Robertght moved this from Needs triage to Triaged in HE Triaging Board (new bugs) Oct 9, 2021
@dpasque dpasque added Triaged To be used when issues have been triaged. [Pod] Flow Patrol (Manage) [Pri] Normal and removed Needs triage Ticket needs to be triaged labels Oct 11, 2021
@dpasque dpasque moved this from Triaged to Prioritized - Bugs in HE Triaging Board (new bugs) Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants