Closed Bug 887783 Opened 7 years ago Closed 7 years ago

[User Story] Cancel a contact import

Categories

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

x86
macOS
defect

Tracking

(blocking-b2g:koi+)

VERIFIED FIXED
blocking-b2g koi+

People

(Reporter: wmathanaraj, Assigned: jmcf)

References

Details

(Keywords: feature, Whiteboard: [TEF][UCID:Comms19, FT:comms, KOI:P1][Sprint 1][Status: pending QA approval], [u=commsapps-user c=contacts p=3])

Attachments

(2 files)

16.27 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document
Details
773.55 KB, application/pdf
Details
User story:

As a user I expect to be able to cancel a contact import, e.g. from facebook, gmail, etc 

Precondition:

* contacts app is open

Acceptance Criteria:

* user is given an option where he can hit cancel of the import
* when cancel is hit the import is stopped safely by dropping any partial contact data.
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/52538225
David Scravaglieri deleted the linked story in Pivotal Tracker
The user story needs to be clarified. 

I guess the correct behaviour would be that the user can cancel an ongoing Contact Importation session. Once the 'Cancel' button is pressed the Contacts importation session will finish with a number n of Contacts imported. The remaining contacts will not be imported. 

Please clarify that this is the correct behaviour.
We need some info on this from Stephany/Ayman as to what the UX guidelines are on the implementation.
Flags: needinfo?(swilkes)
Flags: needinfo?(aymanmaat)
Whiteboard: [ucid:Comms19] → [ucid:Comms19], [u=commsapps-user c=contacts p=0]
(In reply to Jose M. Cantera from comment #3)
> The user story needs to be clarified. 
> 
> I guess the correct behaviour would be that the user can cancel an ongoing
> Contact Importation session. Once the 'Cancel' button is pressed the
> Contacts importation session will finish with a number n of Contacts
> imported. The remaining contacts will not be imported. 
> 
> Please clarify that this is the correct behaviour.

Hey jose, following on from our discussion just formally confirming here that this is the desired behavior.
**PATH**

1) user engages contact import either in FTU or via the contacts app through any of the sources offered.
2) during import the user is given the option to cancel the import
3) user selects option to cancel import
4) import is stopped at the contact that is being imported when cancel is selected.
5) no further contacts will be imported until the import functionality is reengaged by the end user
6) any contact that have been imported during the cancelled import session will not be removed. i.e. cancel is 'cancel' and not 'cancel and undo' 

I will produce a brief wireframe flow to illustrate behaviour

Ping me if you require any further information / clarification in the mean time
Flags: needinfo?(aymanmaat)
Whiteboard: [ucid:Comms19], [u=commsapps-user c=contacts p=0] → [ucid:Comms19], [u=commsapps-user c=contacts p=3]
listed as must have in v1.2 for COMM team. koi+
blocking-b2g: koi? → koi+
Assignee: nobody → jmcf
Depends on: 889769
Clearing the needinfo for me since this is underway with our team (see Ayman's comment 6).
Flags: needinfo?(swilkes)
Whiteboard: [ucid:Comms19], [u=commsapps-user c=contacts p=3] → [ucid:Comms19 KOI:P1], [u=commsapps-user c=contacts p=3]
Referencing comment 6 Wireframes attached.

Wireframes will be part of ContactsV1.2 wireframe pack
Whiteboard: [ucid:Comms19 KOI:P1], [u=commsapps-user c=contacts p=3] → [UCID:Comms19, FT:comms, KOI:P1], [u=commsapps-user c=contacts p=3]
Whiteboard: [UCID:Comms19, FT:comms, KOI:P1], [u=commsapps-user c=contacts p=3] → [TEF][UCID:Comms19, FT:comms, KOI:P1], [u=commsapps-user c=contacts p=3]
Whiteboard: [TEF][UCID:Comms19, FT:comms, KOI:P1], [u=commsapps-user c=contacts p=3] → [TEF][UCID:Comms19, FT:comms, KOI:P1][Sprint 1][Status: pending QA approval], [u=commsapps-user c=contacts p=3]
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.