Closed
Bug 840048
Opened 12 years ago
Closed 12 years ago
[MMS][User Story] Message send failure, resend
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-b2g:leo+)
RESOLVED
WORKSFORME
blocking-b2g | leo+ |
People
(Reporter: pdol, Assigned: cassie)
References
Details
(Keywords: feature, Whiteboard: [LOE:M])
Attachments
(2 files)
UCID: Messages-038
User Story:
As a user, I will be notified if the sending of a message fails and will be given the opportunity to re-send the undelivered message from the application to ensure any composed messages can be sent to their intended recipients
Updated•12 years ago
|
Blocks: mms-userstories
Updated•12 years ago
|
Assignee: nobody → boaz
Comment 1•12 years ago
|
||
Vicamo, can you confirm that the platform support is already in place for handling send failures?
Assignee: boaz → vyang
Comment 2•12 years ago
|
||
The assumption is that this already works with the implementation of SMS, assigning to Bocoup to confirm.
Assignee: vyang → boaz
Updated•12 years ago
|
Assignee: boaz → cassie
Whiteboard: u=user c=messaging s=v1.1-sprint-3 → [LOE:M] u=user c=messaging s=v1.1-sprint-3
Comment 3•12 years ago
|
||
The SMS application UI updates to communicate failed "send" operations.
This behavior confirmed on Gaia@e47143b20 on a B2G device (Unagi) and FireFox Nightly.
Comment 4•12 years ago
|
||
Screen shot showing resend dialog
Upon selecting a message that failed to send, a modal dialog is created confirming a "re-send" operation.
This behavior confirmed on Gaia@e47143b20 on a B2G device (Unagi) and FireFox Nightly.
Comment 5•12 years ago
|
||
I've attached two screen shots to confirm that this behavior is implemented as specified by the bug description. This bug will remain open until such time as the MMS application is complete and confirmed to implement the user story.
Comment 6•12 years ago
|
||
This functionality it's currently implemented. Peter, as you are the reporter, could you close it? Thanks.
Flags: needinfo?(pdolanjski)
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Borja Salguero [:borjasalguero] from comment #6)
> This functionality it's currently implemented. Peter, as you are the
> reporter, could you close it? Thanks.
While it is implemented with SMS, I'd rather not resolve it until we're sure it works with MMS messages as well.
Flags: needinfo?(pdolanjski)
Comment 8•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 9•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
Updated•12 years ago
|
Whiteboard: [LOE:M] [NO_UPLIFT] → [LOE:M]
Comment 11•12 years ago
|
||
Comment #7 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
•