Closed Bug 1099142 Opened 10 years ago Closed 10 years ago

[User Story] Reporting: Requests for conversations

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: oteo, Unassigned)

References

Details

User Story

Enable FxOS Mobile App to send reports about:

1. Number of notifications sent for conversations when trying to reach a contact, including info about:
- Direct conversation? Otherwise selected channel for the notification (SMS, email....)
- Contains subject? (no the subject itself)
- Origin: Loop application´s contact picker, call log, address book
    
2. Number of notifications for conversations received, including info about
- Contains subject? (no the subject itself)
- Result:
    Ok

3. Number of conversations proposal answer received including
- Contains subject?
- Result:
    Ok
No description provided.
User Story: (updated)
User Story: (updated)
Blocks: 1099191
No longer blocks: Loopmov_1_1_1
Depends on: 1098339
Assignee: nobody → opatinobugzilla
Status: NEW → ASSIGNED
Usually user stories are not owned by a dev but the dependencies. Reset owner to default.
Assignee: opatinobugzilla → nobody
Status: ASSIGNED → NEW
Depends on: 1110672
No longer depends on: 1098339
Depends on: 1110675
No longer blocks: Sprin1_loop_1_1_1
After talking with Carmen, I think it's better to close this User Story as invalid. In the current version when we try to make a conversation and it fails, we are going to offer creating a room, we're not going to send a notification anymore. Point 3 was related to the scheduler, and we are not going to implement that functionality. For this reason closing it as invalid.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.