Skip to content

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

Closed

Description

@MitchExpensify

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com 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:
alexandra.ivelisse@team.expensify.com
george.hayakawa@team.expensify.com
simone.avent@team.expensify.com
paige.smith@team.expensify.com
rebeccas.norris@team.expensify.com

Customers:
lisa.barker@aduroadvisors.com
abdulhamid.janat@expensify.partnerhero.com
ac.sloafhouse@gmail.com
andreylazutkinutest+101016@gmail.com
andreylazutkinutest+190920@gmail.com
andreylazutkinutest+230970@gmail.com
krvmznpgq9@privaterelay.appleid.com
jaleman@rosebowlaquatics.org
jeff@runyonrental.com
so@hollywooddivineinc.com
yuriy.turbo+expenses.23.09@gmail.com
marlyn.mathew@zurabio.com

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

image

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

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Oct 19, 2022

    @melvin-bot

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

  2. removed
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Oct 19, 2022
  3. MitchExpensify commented on Oct 19, 2022

    @MitchExpensify
    ContributorAuthor

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

  4. MitchExpensify commented on Oct 19, 2022

    @MitchExpensify
    ContributorAuthor
  5. alex-mechler commented on Oct 19, 2022

    @alex-mechler
    Contributor

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

  6. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 19, 2022
  7. melvin-bot commented on Oct 20, 2022

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

  8. melvin-bot commented on Oct 20, 2022

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

  9. melvin-bot commented on Oct 21, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringImprovementItem broken or needs improvement.ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions