Repository navigation
Conversation
…label The board sharing picker supports users, groups, and teams, but it only requested 20 autocomplete results and displayed the first 10 unallocated entries. This may give the impression that only users are supported. Raise both limits to 200 and use a more specific picker label to clarify the supported sharing targets. The 200-result limit follows established behaviour in Calendar, Tasks, and Bookmarks. Signed-off-by: Max Emig <github@emigm.ax>
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
|
Thanks for addressing this. We reproduced the same issue in our Nextcloud environment. In our case, the group name is also part of many users' email addresses. Therefore the autocomplete returns many matching users before the actual group. With the current We verified the cause by locally changing the frontend limit from 10 to 20. After a hard browser reload, the group immediately became selectable. Increasing the limits to 200 is a clear improvement, but I wonder whether this still leaves the same issue for larger installations. With more than 200 matching users, an exact group match could still be hidden. Would it make sense to prioritize exact matches, especially exact group matches, before applying the result limit? That would make the picker robust regardless of the number of matching users. Environment:
|
The board sharing picker supports users, groups, and teams, but it only requested 20 autocomplete results and displayed the first 10 unallocated entries. This may give the impression that only users are supported.
Raise both limits to 200 and use a more specific picker label to clarify the supported sharing targets.
The 200-result limit follows established behaviour in Calendar, Tasks, and Bookmarks.
Summary
In my local Nextcloud instance, I was only ever suggested 10 users for sharing a board with, the label Select account with the absence of any suggested groups led me to believe that group-sharing was not supported.
It turned out, after searching existing groups are found just fine.
Two improvements to resolve that UI/UX gripe, bump the limit to 200 displayed users/groups/teams to share a board with in line with Calendar, Tasks, and Bookmarks and clarify in the label that teams and groups are also supported.
TODO
n/a
Checklist