2024_07 #story_b: BUG: newly created teams in PROD not created or seen as expected

[ljmoody]

Discovered 7/3/2024 when creating a team live with James. VA laptop. Edge browser. Using my VA email login to and create teams within Sim UI, PROD instance.

What happens now:

Test 1, PROD:

After creating a new team and adding:

• myself, Praxis email, Administrator role
• James, Praxis email, Team Lead role the only team world I see listed is _shared:

The _shared world includes:

I then logged off, and logged in using Praxis credentials:

1. I see these teams listed:
2. The _teams world only has me listed & does not include 6 automatically added individuals
3. The _ind world only has me listed & does not include 6 automatically added individuals

Test 2, PROD:

After creating a new team and adding:

• myself, VA email, Administrator role
• James, VA email, Team Lead role the team worlds I see are:

1. The _team world includes:

   [!NOTE]
   Jennifer is missing.

2. The _shared world includes:

3. The _ind world includes:

   [!NOTE]
   Jennifer is missing.

What should happen:

The behavior of PROD new team creation should be the same as found in TEST:

• Administrators, when using their administrator associated email to login, should see 1) all teams they've joined an 2) ones in which they have an 'Administrator' role.
• All 6 automatically added individuals should be added to all team creations + worlds.
• FYI @tejaspesquare, PROD instance is particularly suspect; behavior seems normal in TEST instance (see screenshots below). Could this issue be related to code migration?

Test 3, TEST:

When live testing with James (Edge, VA laptop, VA login), I created a new team adding:

• myself, VA email, Administrator role
• James, VA email, Team Lead role I see all team worlds:

1. The _team world includes:

2. The shared world includes: ? - Should James also be listed here as Team Lead/VA email_

3. The _ind world includes:

[tejaspesquare]

@jamesmrollins , @ljmoody ,

This looks working fine as expected.

Prod Instance, using 'tejas.p' login:

New Team got created

All 3 worlds got configured with expected default members:

ex. _ind world

Added - Laura Moddy, Praxis email, Administrator role Edited James, Praxis email, Team Lead role from Administrator under _shared world:

Logged in using Laura Moody's Praxis account, only permission granted world is being added which is expected

all 6 automatically added individually are present

If I miss anything, please let me know.

[ljmoody]

@tejaspesquare, I tested as you did and, using your same scenarios I got matching results. Which is good. However, the Sim UI PROD instance is acting strangely for me.

I think something odd could be going on with team creation in PROD. Can you please check? fyi: tested using VA login, PROD instance, Edge browser, VA laptop.

Create a team from Admin Dashboard > Settings > Add, & did not add any members as I created the team:

• I only see the _shared world was created. Am I supposed to see ind and team worlds, too?

Create team from Admin Dashboard > Settings > Add, & added 2 members myself as I created the team:

• I only see the _shared world was created. Shouldn't I also see ind and team worlds, too?

Create a team from Admin Dashboard > Settings > Add.

• I only see the _shared world was created:
• It does contain the 6 auto-added people:

  After creating the base team, used Settings > select team > Edit to add members:

• I manually added 2 more:
• Only 1 of the 2 people I added show on the _shared team list. Shouldn't I see James' VA email/member listed here now?

Checking against Epicenter:

It looks as though all worlds were made for all 3 teams I created, but that's not what appears in the Sim UI:

• I think there could be issues with 1) seeing created worlds & 2) auto-added people and worlds they are added to.

fyi: @jamesmrollins @lijenn

[ljmoody]

7/9/24 response from Tejas: It appears that there is a conflict during team setup calls, as both of yours VA and Praxis have Administrator login access. We will need to investigate further to determine the root cause, and we will provide you with an update once we have more information.

Note: When we used James's credentials, the setup worked well. Not certain but his VA login Id having non-admin access.

[jamesmrollins]

@tejaspesquare please provide a weekending update. Thank you.

[tejaspesquare]

Hello @jamesmrollins The work is still ongoing. The developer is in the process of troubleshooting the code.

[tejaspesquare]

Hello @jamesmrollins , @ljmoody ,

This is got fixed & can be tested on TEST.

Using Laura's VA credentials, Team setup done & all worlds (_Team,_shared & _ind) got created

Checking Respective Worlds with default Members

1. _team World

2._shared world

3._ind world

When login with Laura's Praxis credentials, I see _team & _ind worlds accessible

When establishing a team without including any team members or appointing a Team Lead

Alos, did team setup using Laura's Praxis credentials, worlds got created as expected

Kindly confirm and inform us if you have noticed any discrepancies. If there are any aspects related to the business requirements that we may have overlooked, please share those details with us too.

[ljmoody]

Hi @tejaspesquare - I'll test as you did and outline my experience below. Tested in TEST, Edge browser. fyi: @jamesmrollins @lijenn @matomasz

Test 1: Edge browser, VA login

Created a team.

• Created a team via Settings>Facility Team Setup
• Did not add any members/leads/admin - just kept with the default
• I only see _team and _ind worlds were created (via the Sim UI); however, Epicenter shows that all 3 were created

Checked all worlds for default members.

• _IND world:

• _TEAM world:

• _SHARED world (as shown in Epicenter since not showing in Sim UI): I am not listed as a member

Added myself (Praxis email) as Administrator in _ind and _team worlds.

• Logged in with Praxis credentials
• I also see _shared world - this is correct, since rule is that "Adding a member to _team will automatically add them to _shared and _ind. For this reason, _ind also listed in drop-down."

Test 2: Chrome browser, VA login

Created a team.

• Created a team via Settings>Facility Team Setup
• Did not add any members/leads/admin - just kept with the default
• I only see _team and _ind worlds were created (via the Sim UI); however, Epicenter shows that all 3 were created

Checked all worlds for default members.

• _IND world:

• _TEAM world:

• _SHARED world (as shown in Epicenter since not showing in Sim UI): I am not listed as a member

Didn't have to add myself (Praxis email) to _ind as it was already populated.

• This was not the same user experience as in Edge.
• Logged in with Praxis credentials
• I also see all 3 worlds; this is correct according to permission rules

_I believe I should see the shared world upon team creation since I am an Administrator and am listed in all 3 worlds in Epicenter, correct?

Test 3: Chrome browser, Praxis login

Created a team.

-default members only; did not add any

Checked all worlds for default members.

• _IND world:

• _TEAM world:

• _SHARED world (as shown in Epicenter since not showing in Sim UI):

Note: It is odd to me that under my Praxis login, I am auto added twice (once with VA email, once with Praxis email) onto all teams. Versus under my VA login, where I am auto added once to _ind and _team, but not to _shared.

[ljmoody]

@tejaspesquare -Jenn and I tested this together in PROD instance today - I used Edge, she used Chrome. We both experienced the same issues outlined below:

• When we each created a team and did not specify a team lead, the only team worlds created that we could see were _ind and _team. (But we could each see all 3 worlds that the other had created.)
• When we created a team and DID specify a team lead, we could see all 3 worlds were created.
• Interestingly, the default_team_lead@mail.com user was ONLY added to worlds in which we added a specified team lead. Leads me to think the default user is not being added to all teams, but to teams with leads. Please check into this.
• Also, we both could not see _shared worlds in which we did not specify leads. So there is some type of connection between specifying a lead and not

fyi: @jamesmrollins