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

Double displayname doesn't result in showing the e-mail addres in the share menu #20391

Closed
michaelstingl opened this issue Nov 9, 2015 · 7 comments

Comments

@michaelstingl
Copy link

An user reported:

We noticed that once there are more than one user with exactly the same "Display Name" configured, that the share menu shows all the names, but doesn't show the e-mail address behind it to know which one is which.

Steps to reproduce

  1. Create 2 users
  2. Add the same displayname (John Doe) to both users
  3. Share a folder and start typing "John D…"

Expected behaviour

ownCloud should show additional information (like email) to distinguish users

Actual behaviour

I see both users, but don't know which is the right one

@MorrisJobke Are there any plans to improve this?

00004123

@MorrisJobke
Copy link
Contributor

I just thought about this. It would be ideal to show the email address only if there are duplicate entries. Then I checked the response on an autocomplete request and it doesn't contain any further information.

@rullzer Does it make sense to also deliver the email address (if set) to the frontend. Maybe this is already available as an OCS API and then show this info when it is needed. Or is this too much? Or the wrong approach?

@rullzer
Copy link
Contributor

rullzer commented Nov 9, 2015

@MorrisJobke I would go for the user id (I think we had a ticket about that)... since the e-mail can be empty

@rullzer
Copy link
Contributor

rullzer commented Nov 9, 2015

#20291

@MorrisJobke
Copy link
Contributor

@MorrisJobke I would go for the user id (I think we had a ticket about that)... since the e-mail can be empty

Nah...just think about LDAP ... you won't use the user ID -> it's internal stuff ;)

@MorrisJobke
Copy link
Contributor

Ah okay...let's close this as duplicate

@MorrisJobke MorrisJobke removed their assignment Nov 9, 2015
@rullzer
Copy link
Contributor

rullzer commented Nov 9, 2015

well then we need to think about something generic. Since we can't assume the e-mail is set.

@MorrisJobke
Copy link
Contributor

@rullzer #20291 (comment)

@lock lock bot locked as resolved and limited conversation to collaborators Aug 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants