Closed Bug 1089955 Opened 10 years ago Closed 10 years ago

[User Story] Recurring plan setup

Categories

(Firefox OS Graveyard :: Gaia::Cost Control, defect)

x86
macOS
defect
Not set
normal

Tracking

(feature-b2g:2.2+, tracking-b2g:backlog)

RESOLVED FIXED
2.2 S1 (5dec)
feature-b2g 2.2+
tracking-b2g backlog

People

(Reporter: pdol, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [ucid:SMRTDATA-13-11][NaBfT])

User Story

As a user, I want to be able to configure my Usage app based on my recurring mobile data plan that I have on my SIM card so that the Usage app displays information in a way that is useful to me.

Acceptance Criteria:
1. Choosing a weekly plan recurrence enables the selection of a day of the week as the plan start day.
2. Choosing a weekly plan recurrence updates my usage dashboard upon completion of the plan set up to show the UX by week, as described in the UX spec.
3. Choosing a monthly plan recurrence enables the selection of a day of the month as the plan start day.
4. Choosing a monthly plan recurrence updates my usage dashboard upon completion of the plan set up to show the UX by month, as described in the UX spec.
5. When looking at the usage dashboard, if a monthly start date was chosen that is greater than the number of days in the current month, then the dashboard resets on the first day of the subsequent month.
6. Interaction and Visual Design matches UX spec.
      No description provided.
No longer depends on: 1089954
Whiteboard: [ucid:SMRTDATA-13-11] → [ucid:SMRTDATA-13-11][NaBfT]
Blocks: 1095079
No longer blocks: 1089952
User Story: (updated)
Summary: [User Story] Recurring plan setup [DRAFT] → [User Story] Recurring plan setup
feature-b2g: --- → 2.2?
blocking-b2g: --- → backlog
feature-b2g: 2.2? → 2.2+
Blocks: 1102818
No longer blocks: 1102818
Depends on: 1102818
Closed because the development bugs are finished
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S1 (5dec)
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.