Don't show full name, working hours and local time for invited users

[maxceem]

This is only for invited users.

If we know user handle - show handle (big instead of name).
If we don't know handle - show email (big instead of name).

This task should be also done in Project Service - it should not return full name, working hours and local time for invited users.

[vikasrohit]

@maxceem do you think we would be able to wrap this in Feb release?

[maxceem]

@maxceem do you think we would be able to wrap this in Feb release?

Yes, we can. Should we still show the photo? It feels a photo is also private information and should not be shown for invited users.

[vikasrohit]

Lets not show any info other than handle or email (if invited via email), for the invited users.

[maxceem]

This is done client-side 291570c and server-side topcoder-platform/tc-project-service@e24ea3a.

It has been deployed to DEV and ready for testing.

[nithyaasworld]

@maxceem

1. When invited using handle, it shows a dummy email.
   

2. When invited using email, it shows both email and handle. Please confirm if its okay to show handle if the user is invited by email.

[nithyaasworld]

3. After accepting the invitation, it shows full name, handle and working hours. But Email is not shown. Please confirm if this is okay.

[vikasrohit]

@nithyaasworld
1 .the dummy email is a masked email which we in dev environment all existing users at the time of data load in dev. However, we should not see the email of an invited user if user is invited via handle. I thought we fixed that @maxceem with topcoder-platform/tc-project-service#466 and topcoder-platform/tc-project-service#467.
2. Showing handle for a user invited via email is okay I guess for now, but I would like to ask @maxceem if we can get rid of that as well, if possible. We want to keep the rule simple, for invites user would see what he/she used to invite user.
3. Yes, email should not be shown (except the case where user is invited via email only) for any user except admins.

[maxceem]

@nithyaasworld 1 and 2 the email shouldn't be shown to non-admin users. I cannot reproduce this issue with pshah_manager. Could you, please, let me know which user did you use for testing so you can see emails in invitations?

@vikasrohit regarding 2. At the moment it's not easy to quickly change this. But if we need this we can move towards it during migrating to RESTful invitation API. There is one feature though, which relies on knowing the handle. client-side we validate that already invited is not invited the second time. If we don't do such validation then we could invite the same user by email and by the handle. We can still have this validation server-side though.

[vikasrohit]

@maxceem I am okay with showing handle for now. Lets create separate issue to track the hiding of handle for invites by email. I think we can still show validation errors on client side, once we have the md5 of emails available in the responses of /members and /invites endpoints. At that point, we can equate the md5 of member's email with md5 of invite's email.