-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
Ability to have "Display Name" which is different from username. #1209
Comments
+1 |
+1 please |
+1 👍 |
Would the display name only be for display or would there be any additional uses for it? |
Right now when you register, not sure about ldap, you set your name. Thereafter there was no way to actually change your name and so it was kind of useless. I just opened a pull request, #1211, which adds a field to the account profile where you can change that. I'm wondering if there should be an option per user or site wide which sets whether the username or the _(real)_name is used on the messages list. |
@graywolf336 Thank you. :) I think you should be able to reference the display-name and it will auto-complete to the username when doing an @search in chat. |
@Theaxiom I think it currently does search on the display-name (real name, name) when you go to mention someone. |
@graywolf336 You are absolutely correct, I believe it should be possible to show display names in channel instead of usernames. How feasible is this? |
@Theaxiom Great question, I have not looked into that. I don't imagine it being extremely difficult though. |
This is a very tricky one, and we may have other old issue about the same feature. The big thing here is: performance and scalability. Our data model is denormalized in favor of really high performance with low CPU and Memory usage. So we don't have the real names available on every message, as we have the username copied. But we do understand that in small team, with less than 1k users, we could have a memory map for the real names, and that's what we will do. We will create an setting to turn that on, and recommend that large deployments keep that turn of. |
👍 |
2 similar comments
👍 |
👍 |
👍 I really want this feature. |
👍 |
3 similar comments
👍 |
👍 |
👍 |
@engelgabriel: that implementation is what I'd go for, too. Display names change so rarely, that it's not even worth subscribing to the mapping collection. |
👍 |
1 similar comment
👍 |
👍 It would be reallly convenient indeed. |
Consider this another comment in agreement that this is needed. I'd work on it myself, if I had the time right now. :( My organization can't migrate to RocketChat, as our usernames are rather inconvenient; most other systems we use employ a description or "Display Name" for a user, rather than their username. |
it is a must have. |
This feature is very important for us too. |
+1 |
+9001 |
+1 |
I believe this is implemented and released now. We've been using it for a few weeks. |
You are right. found here #3337 |
Shall I close this? |
I think you can. It's been working for some time now. :) |
Nice to have the "Name" instead of the username on the chat, anyway, we need this on the "mentions" too, otherwise the employees must remember the domain username of the collegues... in some case this is not an option: we use alfanumeric characters, not the name/surname... Will this be implemented? |
It is great that we can now show real names in messages, but in 0.41.0 where this landed, we can now no longer search for people by their real name. If you switch with CTRL+P or try to mention someone this only matches the username. This reduces usability enormously. |
+1 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Yes please, this is important to have! |
@dmanchev This is closed already Follow this to enable: |
this works in messages but does this also work in "roster" ? |
I'd really appreciate this. People choose bizarre usernames. It would be nice if we could tell who everybody was. |
This is especially helpful if you are utilizing a corporate LDAP/Active Directory which is setting your username to some obscure alphanumeric combination.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: