Closed
Bug 840054
Opened 12 years ago
Closed 12 years ago
[MMS][User Story] Deletion of all message threads
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-b2g:leo+)
People
(Reporter: pdol, Assigned: cassie)
References
Details
(Keywords: feature, Whiteboard: [LOE:M])
UCID: Messages-063
User Story:
As a user, I want to be able to delete all message threads simultaneously.
Updated•12 years ago
|
Depends on: b2g-mms-dom-api
Updated•12 years ago
|
Blocks: mms-userstories
Comment 1•12 years ago
|
||
The assumption is that this already works with the implementation of SMS, assigning to Bocoup to confirm.
Assignee: nobody → boaz
There is a "select all" in the edit mode that allows users to delete all message threads simultaneously.
Flagging Peter for NeedsInfo to confirm that the current implementation fulfills this requirement.
Flags: needinfo?(pdolanjski)
Updated•12 years ago
|
Assignee: boaz → cassie
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Casey Yee [:cyee] from comment #2)
> There is a "select all" in the edit mode that allows users to delete all
> message threads simultaneously.
>
> Flagging Peter for NeedsInfo to confirm that the current implementation
> fulfills this requirement.
It does. This requirement is basically in place to ensure that this continues to be the case with MMS.
Flags: needinfo?(pdolanjski)
Comment 4•12 years ago
|
||
Same as in other bugs. We have a huge list of US and bugs which are not consistent with the current implementation of Messaging App. This is working and should be working after MMS integration. We should close this for being consistent with the bug policy: One bug for a real 'bug' or 'feature to be implemented'.
Flags: needinfo?(pdolanjski)
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Borja Salguero [:borjasalguero] from comment #4)
> Same as in other bugs. We have a huge list of US and bugs which are not
> consistent with the current implementation of Messaging App. This is working
> and should be working after MMS integration. We should close this for being
> consistent with the bug policy: One bug for a real 'bug' or 'feature to be
> implemented'.
I'd prefer to verify that this works with MMS first (although it is the same app, this should be a quick verification once MMS is working).
Flags: needinfo?(pdolanjski)
Comment 6•12 years ago
|
||
Per partner and release-driver discussions, marking blocking- until all MMS functionality in bug 849867 is complete, allowing it all to be uplifted at once to avoid SMS bustage.
blocking-b2g: leo+ → -
Updated•12 years ago
|
Flags: in-moztrap?
Comment 7•12 years ago
|
||
leo+ as this is a part of MMS and part of v1.1 to be included in leo+ queries. No_UPLIFT for now before the whole MMS is completed
blocking-b2g: - → leo+
Whiteboard: [LOE:M] → [LOE:M] [NO_UPLIFT]
Updated•12 years ago
|
Assignee: mike → cassie
Comment 8•12 years ago
|
||
Depends on bug 847736 instead of the meta bug. Bug 771458, accept array of message IDs, may be handy here.
Comment 10•12 years ago
|
||
As agreed in Madrid assigned to us https://wiki.mozilla.org/Gaia/SMS by now. I will talk with Steve Chung in order to check who will be in charge of this.
Assignee: cassie → fbsc
Updated•12 years ago
|
Assignee: fbsc → cassie
Updated•12 years ago
|
Whiteboard: [LOE:M] [NO_UPLIFT] → [LOE:M]
Updated•12 years ago
|
Target Milestone: --- → 1.1 CS (11may)
Comment 11•12 years ago
|
||
Comment #5 is a noisy way of doing this. The MMS functionality is an iteration on the existing SMS code. Closing this, and QA will reopen when testing if for some reason the devs regress this functionality.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•