Closed
Bug 813152
Opened 13 years ago
Closed 13 years ago
[<costcontrol/settings>]: Timestamp in cost control settings should match reset cycle dates
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: marcoc, Unassigned)
Details
(Keywords: ux-userfeedback, Whiteboard: UX-QA, Interaction design)
[<costcontrol/settings>]: Timestamp in cost control settings - phone activity and data usage areas should match period set. If Today is the first day in cycle, it should just show Today and time, if it is the second day in cycle, then it should show yesterdays date 'dash' today and time of last update. If data is Reset - should timestamp should start from date of reset.
Environment: Unagi - 20121115171529
Repro: cost control settings in postpaid view
Expected: Timestamp represents first date in cycle set to today and last update time.
Actual: Timestamp represents today's date and last update time.
https://www.dropbox.com/s/at1e8raixrl97wj/2012-11-19-15-59-43%20timestamp.png
Keywords: ux-userfeedback
Whiteboard: UX-QA
Component: Gaia → Gaia::Cost Control
Priority: -- → P1
Whiteboard: UX-QA → UX-QA, Interaction design
Upon discussion with Salva, closing this bug and 813156, and opening new one just for: If Today is the first day in cycle, it should just show Today and time.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•