Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enrich MessageParticipant when we learn about their first name / last name #3945

Open
FelixMalfait opened this issue Feb 13, 2024 · 2 comments
Assignees

Comments

@FelixMalfait
Copy link
Member

I just tested the gmail import feature.

The scenario was the following:
(1) Charles had sent a calendar invite to me an Raphaël, in that invite Raphaël had no display name - only an email
(2) Raphaël sent me an email, he had a proper display name

Because (1) was imported before (2), Raphaël didn't have a full name in Twenty. This should be fixed.

@FelixMalfait FelixMalfait added the scope: backend Issues that are affecting the backend side only label Feb 13, 2024
@bosiraphael bosiraphael moved this from 🆕 New to 🔖 Planned in Product development ✅ Feb 16, 2024
@charlesBochet charlesBochet changed the title Enrich MessageParticipant when we learn about their first name / last name [Timebox] Enrich MessageParticipant when we learn about their first name / last name Mar 19, 2024
@FelixMalfait FelixMalfait changed the title [Timebox] Enrich MessageParticipant when we learn about their first name / last name Enrich MessageParticipant when we learn about their first name / last name Sep 3, 2024
@JorgeGraciaViveros
Copy link

Hi @FelixMalfait ! I am currently working in a group of 5 students from Carnegie Mellon taking a software engineering course and our final project is to contribute to an open-source repo. Our project has multiple checkpoints and will be due on December 8 (meaning our PR will take longer to open). Would it be possible for us to be assigned to this issue (or any issues that you think would be a good fit)? Thanks!

@FelixMalfait
Copy link
Member Author

@bosiraphael what do you think? Does this make sense or is it a bad idea? (there's a risk of overwriting but I'm thinking it's okay to overwrite under some condition like it was createdBy Email integration + lastName is null)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🔖 Planned
Development

No branches or pull requests

4 participants