[$15] UI issue when we invite a member with a long email

[codejamtc]

Expected behavior

The email should be trimmed

Actual behavior

UI issue when we invite a member with a long email

Steps to reproduce the problem

• Login as Customer
• Click on a project that has permission
• Click "Manage Incitations"
• Enter 'pablodiegojosfranciscodepaulajuannepomuceno@gmail.com' > Send Invite

Screenshot/screencast

Environment

• OS: Window 10
• Browser (w/version): Chrome 80.0.3987.149 (Official Build) (64-bit)
• User role (client, copilot or manager): Customer
• Account used: CustomerUser

[maxceem]

In the tooltip we have to make sure, that:

• email or username is cut, so the Invite level is visible, see how it's visible when email or username is short:

  invite by username:

  

  invite by email:

  

• when email or username is cut, we should show an ellipsis ... at the end

In the dialog:

• if we invite user by email, it's already cut, but we have to show elliplisi ... at the ned, now we don't show it:

  

In your PR, please add screenshots on every of 3 cases.

[maxceem]

This issue is open for pickup.

[nahidshahin]

@bug-bash-helper assign

[bug-bash-hunt-helper]

@nahidshahin ✅ you are now assigned to this issue and have 12 hours to complete it.

As soon as you are done, please, make a comment like below, including the link to the pull request:

@bug-bash-helper <link to PR> is ready for review

[nahidshahin]

@bug-bash-helper #3918 is ready for review

[bug-bash-hunt-helper]

@nahidshahin ✅ this issue is marked as Ready for Review.

Now you may pick up another issue which is open for pickup if you like to.

[codejamtc]

Fixed 🆗 https://monosnap.com/file/bqlWIXPlKGDzn24ogu2veH4GNxGN26

[codejamtc]

Partial QA pass in Production: ⚠️

Failed in Firefox @maxceem @vikasrohit

[maxceem]

@vikasrohit how to proceed if issue indeed failed in some case?
Create a new issue for the next release?
Or just keep the current issue as failed and fix it in the next release again?
Or fix it as a hotfix?

[codejamtc]

Fixed in Dev: 🆗

[drasticdpk]

Same issue on prod env /Firefox.
@maxceem how do we know if the issue is ready for prod testing or not ? Can we add new label 'Ready For Prod QA', please suggest.

[maxceem]

@drasticdpk I guess we can let you know on Slack when it's ready for testing as we don't have a special label for this.

[maxceem]

@vikasrohit @lakshmiathreya should we have a special label for such situations?

[drasticdpk]

QA Fail on prod env.

[maxceem]

@drasticdpk issues in milestone 2.9.1 https://github.com/appirio-tech/connect-app/milestone/92 are not yet deployed to PROD.

[vikasrohit]

Can we add new label 'Ready For Prod QA', please suggest.

@drasticdpk @maxceem I don't think we need such label, it would just increase the work for dev team. We are already making notifications about release in Slack with the details of release which has the milestone as well, so it should be pretty straightforward to start testing for certain milestone on prod after we have notified the successful release in Slack.

[drasticdpk]

Verified on prod env

We are already making notifications about release in Slack with the details of release which has the milestone as well, so it should be pretty straightforward to start testing for certain milestone on prod after we have notified the successful release in Slack.

Ok noted cc @vikasrohit

[lakshmiathreya]

Admin view in Prod :