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

Sharee list should not show federation first #15665

Closed
rullzer opened this issue May 21, 2019 · 5 comments · Fixed by #17995
Closed

Sharee list should not show federation first #15665

rullzer opened this issue May 21, 2019 · 5 comments · Fixed by #17995
Labels

Comments

@rullzer
Copy link
Member

rullzer commented May 21, 2019

When entering an email address of a local user the first suggestion is still a federated share. This should not be the case.

sharing_order

Changes are high if the users enters [email protected] they want to share with user0 that has set that as their email instead of a fedeated share.

@rullzer rullzer added bug 1. to develop Accepted and waiting to be taken care of feature: sharing labels May 21, 2019
@rullzer rullzer added this to the Nextcloud 17 milestone May 21, 2019
@MorrisJobke
Copy link
Member

Could be partly solved by #16035

@MorrisJobke
Copy link
Member

I can't reproduce this anymore in master nor in stable16. Seems to be fixed.

@MorrisJobke
Copy link
Member

Found it - if not the full email is entered this is still happening. Sorting up the local user first would solve this.

@skjnldsv
Copy link
Member

Not sure if still happening after #15719

@ChristophWurst
Copy link
Member

Not sure if still happening after #15719

It is. Now showing

user
on bar.com

@skjnldsv skjnldsv removed this from the Nextcloud 17.0.2 milestone Nov 8, 2019
@skjnldsv skjnldsv added 3. to review Waiting for reviews and removed 1. to develop Accepted and waiting to be taken care of labels Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants