Create UMA Histogram on Sources of Where Feedback Reports Are Sent |
||||
Issue descriptionBackground: We plan to only process those feedback reports sent from the "Aw, Snap!" page for crash/bugs update. Con of the plan: We may lose feedback reports sent from other channels, say "help-->report an issue", or hitting the send feedback shortcuts, even though they are related to crash/bugs, because we never process them. Therefore it may be helpful to first track the number of feedback reports sent from these different channels. In the very least case, we should know: x% feedback reports sent from "Aw, Snap!" page. If, say, 95% of feedback reports are sent from "Aw, Snap!" page, then the potential solution (mentioned in background) works perfectly. If in an extreme case (highly unlikely) only 1% of feedback reports are sent from "Aw, Snap!" page, then we will have to refine our solutions. I believe that a high percentage of feedback reports are sent from "Aw, Snap!" page. Let's prove that with data.
,
Apr 27 2017
I think what hzl@ meant here is that for the purposes of following up with users who submitted a Feedback about a Crash, we only want to be following up with those who explicitly submitted it from a crashing page so that we know for sure that a crash id is associated with their feedback.
,
Apr 27 2017
Can you check the OS checkboxes? This is Chrome OS only?
,
Apr 27 2017
It should be all where available.
,
Apr 27 2017
,
Apr 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f4575bd1aaaefd72960d870baca58387ab9b9e95 commit f4575bd1aaaefd72960d870baca58387ab9b9e95 Author: afakhry <afakhry@chromium.org> Date: Fri Apr 28 02:21:04 2017 Add UMA histogram to track the various sources that request the feedback app Basically, it is desired to see how many feedbacks are filed from the sad tab page relative to other sources. BUG= 715682 Review-Url: https://codereview.chromium.org/2844193002 Cr-Commit-Position: refs/heads/master@{#467850} [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/chromeos/arc/arc_session_manager.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/feedback/show_feedback_page.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/supervised_user/supervised_user_interstitial.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/ash/chrome_new_window_client.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/browser_command_controller.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/browser_commands.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/browser_commands.h [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/chrome_pages.h [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/profile_error_dialog.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/sad_tab.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/webui/help/help_handler.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/chrome/browser/ui/webui/settings/about_handler.cc [modify] https://crrev.com/f4575bd1aaaefd72960d870baca58387ab9b9e95/tools/metrics/histograms/histograms.xml
,
Apr 28 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by afakhry@chromium.org
, Apr 27 2017