Remove "Project Role" Selection from Topcoder Team Invitations

[acshields]

Updates - Desired Workflow

1. User clicks "Manage" next to Topcoder Team
2. User enters one or more user handles
3. User clicks "Invite Users"

Updates - Removed Step

Moving forward, the selection of invited user's 'project user role' should no longer be included as a step in the Topcoder Team invitation process.

[RishiRajSahu]

@acshields as per our last discussion If we want to remove selecting different roles while inviting a project, below is the best we could do to achieve this objective -

1. We have notion of Topcoder and Project Roles Currently
2. Whenever a user is invited in Topcoder Team, and if that user posses any of the Topcoder manager role, including Connect Manager the user would be assigned as Manager (Project role) to the project
   Note : Connect Manager is a minimal role to have Project role Manager
3. The ability to change the user roles which we have currently in the Topcoder Team dialog will be removed and it would be implicitly considered that all users in Topcoder Team are managers

Pro - Roles dropdown can be removed

Con - If some user want to all other roles of self/others i.e. if other person is Actually a Account manager or Solution Architect that won't be possible via UI

fyi @vikasrohit

[RishiRajSahu]

@acshields Just for everyone to be on same page I am putting our discussion yesterday here again as final requirements -

1. From now we are going to have single project level manager role
2. Only managers will be invited from Topcoder Team
3. Remove the role switching option from the UI
4. Remove the dropdown of roles when inviting manager
5. We have to check Roles/Visiblity table of ours to verify first if there are anything which visible/hidden if we keep common role for all Topcoder employee for a Project
6. Same goes for the notifications also.

[acshields]

@RishiRajSahu - thank you!

[maxceem]

@RishiRajSahu

1. Should we keep all the specific project roles, or should we completely remove them? This would require us to update project data in the DB and reindex all the projects.

   • Solution Architect
   • Account Executive
   • Account Manager
   • Project Manager
   • Program Manager

2. (If 1. is NO) Currently, we are showing specific project roles as Solution Architect, Project Manager, Manager and so on. Should we keep showing these specific roles, to remove these labels?

   

3. (If 1. is NO) From now on, should we treat all the various manager roles the same? So all the permissions and notifications should be the same for all manager roles.

4. We also have some specific Topcoder Roles which cannot become "managers" but can only become "Account Managers". What role should such users get when we invite them to Topcoder team "managers" or "Account Managers"?

   

[maxceem]

5. There are some notifications which are sent to the specific manager roles:

   • When project is created, Account Managers and Business Development Representatives get notifications
   • When project is ready for review, Account Managers and Business Development Representatives get notifications

6. On the other hand, account_executive Project Role doesn't get any notifications at the moment.

[RishiRajSahu]

@maxceem

1. Let's keep our frontend code backward compatible instead of doing DB updates i.e. if any of such older roles found we have treat them as new common project-manager role.
2. We don't have to show separate roles now on, in-fact we don't have to show any role as the dialog itself defines the roles of the members present under it.
3. Yep unless they have some different permissions/notifications associated with them.
4. All Topcoder roles should atleast have Connect Manager to become manager.
5. Yes we have to update front-end config and backend to honour this still based on Topcoder role of the user
6. same as 5

[maxceem]

@RishiRajSahu to sum up, I guess the logic here would be the next:

• we keep all the Project and Topcoder roles as they are internally, but never show these roles to the users

• when we invite a user manager, the manager is invited using they DEFAULT role as per matrix:

  

• this way all the current permissions and notifications would work the same as before, as all the users would have the same Project and Topcoder roles

7. Updated, see 8. There is only one thing we have to update in the Project Service. Currently, when we are inviting manager users, we can invite several users, but we should invite them with the same role:

   

   We have to update Project Service so we can invite users with multiple roles, for example, maxceem1 as Manager and maxceem2 as Account Executive.

   These is needed, so if user enter multiple managers to invite, for each user we detect they default Project Role and invite each user using this default role, which can be different for each user.

8. There is an easier approach than suggested in 7. We let all the users with any kind of manager roles join with a single Project Role - manager. So inside the Connect App, all the managers would have the same permissions. And notifications would be still handled differently based on the Topcoder Role. I guess this is what was your intention from the beginning.

What do you think?

[RishiRajSahu]

@maxceem a user could have more than one Topcoder roles attached that's why I mentioned that when any user is invited via Team Manager dialog, that user should atleast have Connect Manager(other Manager roles may or may not be present).

Task	Could be Assigned Project Manager
'Connect Admin'	✓
'administrator'	✓
'Connect Manager'	✓
'Connect Account Manager'	_
'Connect Account Manager'	✓
'Connect Copilot Manager'	_
'Connect Copilot Manager', 'Connect Manager'	✓
'Business Development Representative'	_
'Business Development Representative', 'Connect Manager'	✓
'Presales'	_
'Presales', 'Connect Manager'	✓
'Account Executive'	_
'Account Executive', 'Connect Manager'	✓
'Program Manager'	_
'Program Manager', 'Connect Manager'	✓
'Solution Architect'	_
'Solution Architect', 'Connect Manager'	✓
'Project Manager'	_
'Project Manager', 'Connect Manager'	✓

8. Yep that's what I preferred that we have notifications based on Topcoder roles only

also, regarding permissions I guess as we refactor code to have single project manager role those would be handled.

[maxceem]

Thanks for the table @RishiRajSahu it helps.

From this table, it follows that if some user has the only a role like Project Manager or Connect Account Manager then such a user cannot join the project as Manager to the Topcoder Team. Though, previously such users could join a project to the Topcoder Team with a specific Project Role like project_manager or account_manager.

2 questions raise from here:

9. If some user with the role Connect Account Manager (without Connect Manager) is invited to the Topcoder Team should such invitation be refused?

10. We already might have projects where some user with only Connect Account Manager is a member of the project and has account_manager role. Should such a user still be a member of the project? Because as per the table above, such user cannot be a member of the Topcoder Team because doesn't have Connect Manager role.

[RishiRajSahu]

@maxceem , yes Connect Manager role is must now, any other Role(s) could be there or not doesn't matter.
9. updated the table
10. Existing members should be shown under Manager Team only without any role label, should that be an issue ? I guess existing members could be rendered as it is, its only the new member invited who are going to affect , that's what I mean't by backward compatible earlier. Please let me know if I am missing anything here ?