Bug 327315 - KAddressbook should group contacts with same displayed name in list of contacts
Summary: KAddressbook should group contacts with same displayed name in list of contacts
Status: REPORTED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: 4.11.2
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-08 16:51 UTC by bastian löher
Modified: 2021-03-09 02:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bastian löher 2013-11-08 16:51:06 UTC
KAddressbook lists by default all contacts from all resources. Contact items that are in actuality describing the same person but originate from different resources (e.g. from Facebook, Owncloud, local, etc...)  should be consolidated into meta contacts for displaying.

Reproducible: Always

Steps to Reproduce:
1. Add more than one Contacts resource in Akonadi
2. Open KAddressbook
3. Add the same contact to each resource
Actual Results:  
Each contact is listed for each resource separately.

Expected Results:  
Duplicate or Equal contacts should be consolidated into a single meta contact.

Three cases have to be distinguished:

1. The two contact items contain the SAME data, but on different resources (i.e. a local copy + a copy on a cloud instance). In this case only one set of data should be shown.

2. The two contact items each contain only part of the information on the person (i.e. the Facebook account would usually carry different info compared to the cloud contact). In this case both data sets should be displayed.

3. The two contact items have the same name, but describe DIFFERENT people. This means there also has to be a way to avoid grouping on a per-contact basis.
Comment 1 Laurent Montel 2013-11-09 08:17:39 UTC
I confirm it.
We need to fix it.
Comment 2 Justin Zobel 2021-03-09 02:34:23 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.