#admins rooms tied to Collect or Control policies not showing in search or LHN for assigned Guides

[MitchExpensify]

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:

Note: (How do I test 121 assigned guides on dev?)

1. Non paying user creates a Collect or Control policy and is assigned a Guide (Guide gets added as a policy admin)
2. The #admins room tied to that policy shows in LHN for the Guide logged in New.expensify using their team.expensify.com account
3. The Guide uses the search feature in NewDot, typing the policy name, to find the #admins room of the Collect or Control policy

Expected Result:

1. The #admins room tied to the Collect or Control policy shows in LHN for the Guide logged in new.expensify using their team.expensify.com account
2. The #admins room tied to the Collect or Control policy is discoverable via search for the Guide logged in new.expensify using their team.expensify.com account

Actual Result:

1. The #admins room tied to the Collect or Control policy does not show in LHN for the Guide logged in new.expensify using their team.expensify.com account
2. The #admins room tied to the Collect or Control policy is not discoverable via search for the Guide logged in new.expensify using their team.expensify.com account

Workaround:

They can find assignments be logging into expensify.com and looking at their policies list. They can then follow up via email.

Platform:

Where is this issue occurring?

• Web
• Desktop App

Version Number:
Reproducible in staging?:
Reproducible in production?: Yes
Email or phone of affected tester (no customers):

Guides:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Customers:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Issue reported by: Mitch
Slack conversation: Reports from Guides here and more reports from Guides here

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @puneetlath (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[MitchExpensify]

cc @alex-mechler for thoughts on this as he is one of the closest to the code

[MitchExpensify]

Asked if this is a fire here - https://expensify.slack.com/archives/C03U7DCU4/p1666201675400019

[alex-mechler]

1:1'd Puneet, taking this over since I think i know what is happening here

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

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

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