Closed Bug 927896 Opened 8 years ago Closed 8 years ago

[User Story] [DSDS] Import contacts from the "default" SIM during FTE

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+)

VERIFIED FIXED
1.3 Sprint 6 - 12/6
blocking-b2g 1.3+

People

(Reporter: noemi, Assigned: arcturus)

References

()

Details

(Keywords: feature, Whiteboard: [ucid:Comms36, ucid:DSDS20, ucid:DSDS22, 1.3:p1, FT:comms])

As I user, I should be able to import contacts from the "default" SIM during FTE(*)

(*) description based on FTE just handling the "default/preliminary" SIM card

Acceptance Criteria:
* I am able to import contacts from the "default" SIM during FTE when SIM is unlocked
* I am not able to import contacts from "default" SIM if it is locked (SIM PIN status)
* After the FTE I will be able to see all contacts that I have imported listed in the contacts app and could be edited
* I am not expecting to see any marker to differentiate from which SIM (subscription) the contacts have been imported
Keywords: feature
Whiteboard: [ucid:Comms36, ucid:DSDS20, ucid:DSDS22, 1.3:p2, FT:comms]
add moztrap link.
Blocks: b2g-dsds-1.3
moving this to committed as some work must be done to make contact import working in FTE, or else FTE contacts import will be broken
Blocks: comms_1.3_committed
No longer blocks: comms_1.3_targeted
blocking-b2g: --- → 1.3+
Whiteboard: [ucid:Comms36, ucid:DSDS20, ucid:DSDS22, 1.3:p2, FT:comms] → [ucid:Comms36, ucid:DSDS20, ucid:DSDS22, 1.3:p1, FT:comms]
Assignee: nobody → francisco.jordano
Target Milestone: --- → 1.3 Sprint 6 - 12/6
We addressed this changes in the contacts dsds support, since the amount of work was ok
Depends on: 940913
Resolved in bug 940913
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Verified on Fugu.

Gaia:     f64d282b6b44eaaf8cddc8be8f3250cb6fbacd95
Gecko:    0e3362fb5625eb6d98c7617b1b3019a2cc553d47
BuildID   20131202094818
Version   28.0a1
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.