"Workspace chat" is focused in the background instead of admin chat

[kavimuru]

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

---

Issue was found when executing #11565

Action Performed:

1. Create a new account on OldDot
2. When you first login go to Settings > Policies > Group
3. Click on "Select" on the free plan card
4. You should be take to NewDot with the new workspace settings open in the sidebar and the admins room chat focused in the background

Expected Result:

The admins room chat focused in the background

Actual Result:

Workspace room chat focused in the background

Workaround:

unknown

Platforms:

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

• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.67-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Bug5928790_11565_Web.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @mateocole (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[MelvinBot]

@madmax330 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[madmax330]

Testing this today

[MelvinBot]

@madmax330 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[madmax330]

Hmm I'm able to repro this on prod, but I can't repro it locally 😕

[MelvinBot]

@madmax330 this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[madmax330]

This isn't a WAQ issue because it's for a feature that's not yet released

[madmax330]

Didn't have time to look into this.

[madmax330]

No update

[madmax330]

Going to close this, doesn't seem like a priority