nextcloud / nextcloud/spreed

Phone number integration only applying in Talk contacts

Open
#17,068 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: conversations 👥
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

I'm running Nextcloud v32.0.1

At first I thought phone number integration wasnt implemented but i noticed that the contacts are synced when adding someone to a conversation but it doesn't sync their contact in the conversation.
I'm not sure if this is intended functionality but I would really like to see contact names synced in the conversations. this give more customization if someone has a nickname they don't want shared with the whole company. In my use case I use Nextcloud for home use and it would be so much easier to have everyone be able to just sync their contact names for everyone else.

Here's some pictures from my instance:
image
Here's the image of the conversation

image
And here's a image of the Nextcloud contact library

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior on Nextcloud v32.0.1 by comparing a contact synced when adding someone to a conversation with that person's contact in an existing conversation. Start by tracing the Talk contact and conversation integration; done means contact names sync into conversations without requiring company-wide sharing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.