Please list any "footguns" or instances of really bad UX in the current Telemetry dashboard (http://telemetry.mozilla.org). We'll fix these ASAP.

• [FIXED] Users can't find additional filter criteria because it looks like product+histogram+submission_reason are the only available filters
• the "reason*" field is useless -- it's always going to be "saved_session" since idle-daily isn't even supported right now[removing that for a while]
• By default, users will see Telemetry from all products (Firefox desktop + Fennec + B2G + ESR) -- the default filter should be "Firefox", not "any product"!
  • (Should people even be allowed to view data for "any product"?)
    • Good point, they shouldn't be able to
• We need a warning indicating that Telemetry data is missing/skewed since E10S was turned on by default on Nightly (in Nightly 36 on Nov 7th)
• When there are many buckets defined in a histogram measure, the labels in the histogram chart overlap and are illegible
  • hard to fix - not hard if we switch to other lib(really hope that happens) or recompute the buckets
• It's not possible to combine multiple values... Example: drill down to windows select every OS version except NT 10.0 (what is that anyway?)
  • What is the use case for this? It's tricky from UX point of view
• Use meaningful names in the OS version selector: 5.1 = XP, 6.1 = Windows 7
• percentiles are estimated! Interpretation of them should be done with great care. We just throw them at people, as if they are true
  • can you clarify how they are estimated?
• Date range selector is invisible until you know it's there (suggestion: start_date and end_date pickers?)
  • that's a good idea!
  • Put a date picker in Preferences box
• Clearer text for the summary box!
• More tooltips everywheeeere
  • It's unclear what exactly the numbers in the "Summary" side panel refer to (it refers to the currently selected date range)
• Expose addon histograms (Firebug is now sending them in addition to pdf.js and shumway)
• [FIXED] Unable to track histogram buckets over time. e.g. if I have a probe with 3 values (1, 2, 3), I want to be able to see the proportion of the values 1, 2, & 3 over time on a graph. Right now I can only see a histogram for the whole time period. Example: https://telemetry.mozilla.org/#filter=nightly%2F36%2FSAFE_MODE_USAGE I want to see how/when the values "2" and "3" change over time to know that something is causing problems. –MattN
• [FIXED] I preferred how the old dashboard worked where I could select a probe before selecting a product version and then I could see the graph for all versions in the event I want to see the trend for more than just one release. e.g. see how a probe change since it was added in Fx29 until now. Currently I would have to manually add a series for each version of Firefox from 29 through to 36 which is tedious. –MattN
• Overall there is too much attention put on the # of submissions which can be irrelevant for most probes as it basically mirrors the number of people who have telemetry submissions turned on (and therefore doesn't vary between probes). This may not be true for some probe types but I'm not sure. Example: https://telemetry.mozilla.org/#filter=nightly%2F36%2FSAFE_MODE_USAGE The # of submissions there is the same as other probes. The important part is the histogram which is at the bottom. –MattN