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

Concierge - Concierge not displayed for new Employees added to collect policy #51262

Closed
1 of 8 tasks
izarutskaya opened this issue Oct 22, 2024 · 6 comments
Closed
1 of 8 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. DeployBlocker Indicates it should block deploying the API DeployBlockerCash This issue or pull request should block deployment Engineering Hourly KSv2

Comments

@izarutskaya
Copy link

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: 9.0.52-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Can't log in in new account
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5109947&group_by=cases:section_id&group_order=asc&group_id=296773
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Setup - NewDot

  1. Navigate to the collect workspace settings
  2. Navigate to more features
  3. Enable workflows
  4. Navigate to workflows
  5. Enable Approvals
  6. Enable delay submissions and set it to Manually
  7. Invite a new user as an employee (must be Gmail)
  8. Login as the employee account in NewDot in Incognito

Expected Result:

New Employees that are added to a collect policy should initially display the Concierge chat after login in for the first time.

Actual Result:

Concierge not displayed for new Employees added to collect policy after login in for the first time

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6642029_1729601963323.screen-capture__17_.mp4

View all open jobs on GitHub

@izarutskaya izarutskaya added DeployBlockerCash This issue or pull request should block deployment Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. DeployBlocker Indicates it should block deploying the API labels Oct 22, 2024
Copy link

melvin-bot bot commented Oct 22, 2024

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

Copy link

melvin-bot bot commented Oct 22, 2024

Triggered auto assignment to @tylerkaraszewski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

Copy link

melvin-bot bot commented Oct 22, 2024

💬 A slack conversation has been started in #expensify-open-source

@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Oct 22, 2024
Copy link
Contributor

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@izarutskaya
Copy link
Author

izarutskaya commented Oct 22, 2024

In stg opened WS chat, in Production opened # announce room

Recording.2871.mp4

I add 2 labels Deploy because I can't check it with stg server

Screen.Recording.20241022.182330.mp4

@yuwenmemon
Copy link
Contributor

Discussed here: https://expensify.slack.com/archives/C07J32337/p1729633880305189

Closing. This isn't a bug but rather than the intended behavior for a workspace with less than 3 employees: #34929

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. DeployBlocker Indicates it should block deploying the API DeployBlockerCash This issue or pull request should block deployment Engineering Hourly KSv2
Projects
None yet
Development

No branches or pull requests

4 participants