Allow teams to be handled like address books
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
Is your feature request related to a problem? Please describe.
At the moment a team cannot be shared like an address book. If you only want to share address records of team mates and not full address books, you have to create separate address books for each team. It could happen that a person is part of different teams, because e.g. he/she works on multiple projects in parallel. This would require to maintain multiple redundant records for each person.
Describe the solution you'd like
Instead of creating separate address books for each team, with all the contact details copied over, it would be nice to handle a team like an address book. This would allow to maintain personal data in only one record instead of multiple ones. By setting a team specific parameter it should be decided if a team should be handled like an address book or not.
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 names no files, tests, or entry points. Start by tracing how teams, address books, and contact sharing are represented, then determine where a team-specific address-book setting would belong. Done means a team can be configured for address-book handling while its members’ personal records remain maintained in one place.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100