Option to merge contacts by number not by name
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reading the existing contact-merge option and tracing where merge-by-name is applied; the issue does not identify files or tests. Check how phone numbers are compared and whether email-based matching is part of the existing flow. Done means users can choose to merge by number instead of name, without combining different contacts that share a name.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
From what I can tell currently contacts will only merge by name if the option is enabled. This means that different people with the same name can get merged.
I would prefer not to need to add info to the names to differentiate them (Bob 1, Bob 2, etc)
The real unique bit of information is the number (at least in my case, could be email for others). If the merge happens by number then each person is merged at least regarding things like whatsapp/telegram/signal, but the individuals would stay separated.
Why do you want this feature?
Would work better in my use case and I presume for others.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 917
- Forks
- 73
- Avg merge
- 5d 8h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Contacts
-
feature request needs triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
FossifyOrg/Contacts#176 · 1 comment ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 64/100
FossifyOrg/Contacts#618 ·
Maintainers usually reply within 4 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 65/100
FossifyOrg/Contacts#614 · 1 comment ·
Maintainers usually reply within 4 days
-
New field: IBANOpenfeature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Contacts#613 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 52/100
FossifyOrg/Contacts#612 · 5 comments · 1 reaction ·
Maintainers usually reply within 4 days
All issues in FossifyOrg/Contacts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
supabase-community/supabase-kt#1413 ·
Maintainers usually reply within 5 days
-
Type: Possible bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
spacecowboy/Feeder#1258 ·
Maintainers usually reply within 1 day
-
[Submission] 抖音火山版Opensubmit-adaption submit-adaption-pre
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
BetterAndroid/android-notification-icon-project#744 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pedroSG94/RootEncoder#2213 ·
Maintainers usually reply within 2 days