nextcloud / nextcloud/contacts
Improve handling of Contact groups
Open
Nobody has claimed this yet.
0. Needs triage
enhancement
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Is your feature request related to a problem? Please describe.
Actually the handling of contact groups is really confusing for new users.
- If you create a new group and click on the menu "contacts" (Contacts are reloading) the group doesn't exists. This is really confusing new nextcloud users.
- Actually it seems not to be possbile to move more than one contact to another group. Example: I want to delete a group and needs to move every single contact to another group. After this I need to reload the page and the group is removed.
Describe the solution you'd like
- When a user creates a new group it should be saved immediately. It shouldn't matter if the group contains contacts or not. Additionally the user must have the option "Delete" to delete the group. If a user deletes a group that contains contacts a dialog should be display where the contacts should be moved before deleting.
- Batch operation for moving contacts to other groups should be supported (maybe for other operations like delete of a contacts too).
Describe alternatives you've considered
No response
Additional context
No response
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 does not name files or tests, so first locate the contact-group creation, deletion, and contact-selection flows in the JavaScript app. Define the behavior for saving empty groups, deleting groups with contacts, and moving multiple contacts, then verify each flow in the UI, including the requested confirmation dialog and reload behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100