If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Remember user 's preferred view of crash-stats

RESOLVED FIXED in 43

Status

Socorro
Webapp
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: bajaj, Assigned: peterbe)

Tracking

unspecified
x86
All

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

5 years ago
In the meeting between JS team & socorro to discuss user stories , one of the ideas which came across was to have user specific views.

Example Scenario : Some people prefer to view crash-stats by buildid instead of by date which is the default now.

One of the ideas to implement this by Ted/Laura was to : 
* set a cookie to remember the user's preferred view ]

Updated

5 years ago
Summary: Having user preferred views of crash-stats → Remember user 's preferred view of crash-stats
Target Milestone: --- → 40

Updated

5 years ago
Assignee: nobody → peterbe
Target Milestone: 40 → 42
(Assignee)

Comment 1

5 years ago
Pull request here: https://github.com/mozilla/socorro-crashstats/pull/320

:rhelmer r?
Target Milestone: 42 → 43

Updated

5 years ago
Whiteboard: [qa+]

Comment 2

5 years ago
Commit pushed to master at https://github.com/mozilla/socorro-crashstats

https://github.com/mozilla/socorro-crashstats/commit/9be7ec936904ac581621283b8c0effef294d84e8
fixes bug 840240 - Remember user 's preferred view of crash-stats, r=rhelmer

Updated

5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Comment 3

5 years ago
Minimal steps to reproduce:

1. Go to the home page
2. Click the "By Build Date" link near the center-top (it loads a different graph)
3. Click Top Crashers in the lower left-hand corner. 
4. Expect that "By Build Date" is now already selected
5. Go back to the home page (...by clicking the logo in the upper left-hand corner for example)
6. Expect "By Build Date" to be selected and highlighted. NOT "By Crash Date"
You need to log in before you can comment on or make changes to this bug.