Closed
Bug 1080816
Opened 10 years ago
Closed 10 years ago
ditch chart on public dashboard
Categories
(Input Graveyard :: Dashboard, defect, P2)
Input Graveyard
Dashboard
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: u=user c=dashboard p=1 s=input.2014q4)
The chart on the public dashboard is just terrible. It tells you things with lines and colors, but they're all lies, misrepresentations and untruths. It's a mish-mosh of unrelated data clumped together as if it means something. It could be mistaken for modern art. This bug covers the following changes to the public dashboard: 1. ditch the chart 2. make the search widget a first-class citizen at the top of the page 3. (possibly) adjusting the things in the right-most column to talk about Input and User Advocacy and linking to the blog, etc Things to keep in mind: 1. we want to make sure people know the chart is going away before we make it go away--we can probably do this in a blog post 2. we should push the changes somewhere where the UA folks can play with the results and approve them--we can do this with an A/B test where everyone sees A, but you can see B if you give it the right querystring params.
Assignee | ||
Comment 2•10 years ago
|
||
Blog post here: http://bluesock.org/~willkg/blog/mozilla/input_removing_chart.html That's syndicated on Planet Mozilla, so folks should see it.
Assignee | ||
Comment 3•10 years ago
|
||
In a PR: https://github.com/mozilla/fjord/pull/371
Assignee | ||
Comment 4•10 years ago
|
||
Landed in master: https://github.com/mozilla/fjord/commit/d5b35a228e989431a39fb30c719bc6fd7f8f23ce
Assignee | ||
Comment 5•10 years ago
|
||
Pushed to production and I flipped the waffle flag on Thursday. Marking this as FIXED.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Whiteboard: u=user c=dashboard p= s=input.2014q4 → u=user c=dashboard p=1 s=input.2014q4
Updated•7 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•