nextcloud / nextcloud/contacts
MORE INFO (template and menu)
Nobody has claimed this yet.
- 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.
drop down menu to add 'more info' asks 2 clicks to add a note.
we use Notes for every single contact, because we need to qualify contacts.
Isn't NC mainly used for business reasons? Default phone and home are set to Personal.
That's two more clicks for each new contact.
Describe the solution you'd like
Could all options be in the first drop down menu?
Could Notes be added to the default display?
Could we save one (or more) default display/view of contacts to accelerate daily usage of the app?
Describe alternatives you've considered
The side-list of contacts shows their email address under the name of the contact, which is useless as no one will write down this email address on a paper to send an email but will click the mailto: link or copy and paste it.
A small icon showing that an email address has been set for the contact could be useful.
As we have a long list of contacts, showing the company name of the contact, or give users the possibility to choose which detail should be displayed under the contact name would be great option.
Also, the possibility to filter contacts by Company, Country or Town would be very useful.
Additional context
I hope you'll find these ideas relevant ✌️
and thank you for the great latest improvements of this app 👍
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
Start by reviewing the contacts app UI entry points for the More info menu, contact detail display, and side-list rows. The request contains several separate display, default-view, and filtering ideas, so first narrow it to one agreed behavior. Done should be a clearly specified user-facing change with its scope and acceptance criteria confirmed.
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
- Needs clarification
- Newbie friendliness
- 25/100