Bug 333739 - Make it possible to configure which contact is the "primary" contact of a metacontact
Summary: Make it possible to configure which contact is the "primary" contact of a met...
Status: REPORTED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: contactlist (show other bugs)
Version: 0.8.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-22 20:34 UTC by Thomas Pfeiffer
Modified: 2014-04-22 20:34 UTC (History)
0 users

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 Thomas Pfeiffer 2014-04-22 20:34:45 UTC
Currently when merging two contacts, there is no way to influence which contact becomes the "primary" one for the metacontact.
This is a problem if for example that person prefers one protocol for communication when online in both, but the contact from the other protocol is selected as primary.

This may sound like a geeky edge-case, but it's very real for example in the case of my girlfriend. She has a Google+ account, but for chatting, she only uses ICQ. However, her Google contact is still in my contact list since we of course circled each other. Therefore if she logs into Google+ and I write a message to her metacontact, it goes to her G+ even if she already closed the tab.
It's similar with Hangouts vs. Jabber: I prefer open protocols, so I want to chat with people via Jabber whenever possible, but if KTp/KPeople decides to make someone's Hangouts contact the primary one, it's actually more cumbersome (and downright impossible from the Contact List Plasmoid) to talk to that person via Jabber when he or she is online in Hangouts.

Reproducible: Always

Steps to Reproduce:
1. Merge two contacts

Actual Results:  
You cannot influence which one is the primary

Expected Results:  
You can select which contact to make the primary one.