QA Jira clean-up, in agreement with PMs. Bulk-closing 672 tickets in this first batch: Resolved 28 Sep 2021 and older, won't fix/won't do/invalid, NOT community- or customer-bug

project = MM AND issuetype in (Bug, Story, Task, Sub-task) AND status = Resolved AND resolved <= -78w AND resolution in ("Won't Fix", Invalid, "Won't Do") AND (labels not in (customer-bug) OR labels is EMPTY) AND (labels not in (community-bug) OR labels is EMPTY) ORDER BY labels ASC, lastViewed DESC

Closing and moving to ProductBoard for prioritization

It was as a guest. Thank you for the analysis as well. I will transfer this to the Platform Backlog and we will address there.

Thanks for that detailed, analysis, ! , it sounds like this a transient issue that only occurs when transitioning to a guest.

Can you verify this is the context in which you observed the problem? If so, can you provide direction on priority here, and whether this should be treated as a guest accounts-specific issue or a bots-specific issue?

I was able to reproduce this with the following steps with a fresh install:

• Create one user so there is just this user and the sysadmin. Neither user is a guest.

• Login with the two users on different browsers/icognito

• Open the Create DM modal as the regular user

• You should see “3 of 3 members”, which includes the SurveyBot.

• Have the sysadmin user demote you to a guest.

• Open the DM modal again. It will show “3 of 2 members”.

• Refreshing and opening the modal results in it showing “2 of 2” members properly

• Promoting to user before refreshing results in “3 of 3 members”

In summary, demoting a user to a guest causes odd behavior until they refresh. Guests don’t see bots in the list, but it is still being counted in the total because the data is still in the redux store.