Closed Bug 1008105 Opened 11 years ago Closed 10 years ago

[User Story] As a user I would like to be able to use the details of an entry in the Loop communication history to create a new contact or add them to an existing one

Categories

(Firefox OS Graveyard :: Gaia::Loop, defect, P1)

Product:
Firefox OS Graveyard
Component:
Gaia::Loop
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: oteo, Unassigned)

References

Details

(Whiteboard: [ucid:WebRTC26,2.0, ft:webrtc])

User Story

When I am browsing my communication history in Loop, if an entry is not already linked to any contact in my device Address Book, I can decide to use that entry information (MSISDN or e-mail) to:

   - Create a new contact
   - Add the Loop ID (MSISDN or e-mail) to an existing contact

If by any reason, the ID is not available, this option won’t be available.

This is achieved by a long-press on the call log entry and then selecting in a menu the operation to be done (add to existing, create new one). 

Implementation Note: Since this moment on, until the contact is created/updated, the operation is handled by the Contacts Application which is invoked via Activities (similar to what the Dialer Call Log currently does)

Note: UX Details should be specified in Wireframes
No description provided.
Blocks: loop_call_log
User Story: (updated)
User Story: (updated)
Summary: As a user I would like to be able to use the details of an entry in the Loop communication history to create a new contact or add them to an existing one → [User Story] As a user I would like to be able to use the details of an entry in the Loop communication history to create a new contact or add them to an existing one
Priority: -- → P1
Whiteboard: [ucid:WebRTC26,2.0, ft:webrtc]
Depends on: 1023760
Depends on: 1034544
Depends on: 1034550
Adding in the US that if the ID is not available the options of creating a new contact or adding it to an existing one will not be available.
User Story: (updated)
Depends on: 1035693
Depends on: 1036309
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.