For large instances users need to know whether share recipient has Nextcloud account or not
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
[!TIP]
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
Is your feature request related to a problem? Please describe.
In commit ae854e0dd2c52693e9c5257141710d9c0f1f8276, the previously combined input field for internal and external shares has been split into two separate input fields.
In a large company with many employees, some of whom are external project team members with accounts in the Nextcloud instance, the problem now arises that users need to know whether the person they want to share something with has an account or not.
Users who are unaware of this will be confused if they enter an external email address in the lower field and receive the message "no elements found".
I've searched through all the issues and haven't found anything related to this: Is anyone else experiencing this problem, or does anyone have any ideas on how to solve it?
Describe the solution you'd like
It would be great if there were a option to have only one input field as before, or to have both input fields recognize internal accounts as well as external email addresses and display them in the correct area after adding them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue references commit ae854e0dd2c52693e9c5257141710d9c0f1f8276; start by examining the split internal and external share inputs and the sharing UI entry point. Determine how the recipient search distinguishes account holders from external email addresses, then verify that the chosen unified or separate-field behavior presents both correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cloud, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100