Request to enhance Chromeos feedback reports with user provided time estimate |
||||||||
Issue description
Currently, the feedback reports submitted by users are often a bundled tarball of the different system logs, along with (hopefully) a few lines of problem description by users. However, developers are often left wondering as to how to correlate the logs with user experiences.
For e.g. from the user statement "The screen flickered for a few seconds", it is very difficult to relate to the logs around what time stamp to look around for issues.
Thus, it will be very helpful if while submitting the feedback logs, there could be an optional field that could ask users something like "Around what time was the issue seen - make a best guess" and enter HH:MM:SS or (less desirable) "How long ago did you see the issue". Or may be something that lets user specify a range ("the problem happened between 2-3 PM on 1/4/1028" etc).
Essentially this helps by giving some hints into around what time to look for problems.
This request came from Intel, but I too think this will be very helpful. I don't know how to go about finding an owner for this, but I'll copy some folks and may be they can help in finding the right team.
,
Jan 9 2018
Thanks Rajat for the great description, appreciated! > or (less desirable) "How long ago did you see the issue". Less desirable but not so bad if the time when the report was submitted is easily found. > Or may be something that lets user specify a range I think free-form should be at least a possibility to allow answers like "5 times in the last hour" or "every 10-20 seconds since I opened that page 3 minutes ago". The form should also feature some sample answers like these to help submitters understand the purpose.
,
Jan 10 2018
,
Feb 6 2018
Any ideas on who should own this?
,
Feb 6 2018
It's a UI issue, maybe Zel can direct this. Basically you're saying that we should gently guide users to provide more useful information. Right now the only guidance we give is the writing "Tell us what's happening" at the top, which is concise and non-scary. Surely the goal here is to encourage sending feedback, by minimizing obstacles, including the merely psychological ones. Maybe that writing could be a link to a page with more detailed instructions, which would also contain "please include the time of the incident(s), even as a rough guess". Anyway, I'll stop bikeshedding now.
,
Feb 6 2018
gracec@ this is the feedback UI we were discussing your team possibly taking on.
,
Feb 6 2018
Ownership of the feedback UI is in transition. I'm going to leave this one on my plate for now until gracec@'s team is ready to pick things up.
,
Feb 7 2018
> > "Tell us what's happening" > at the top, which is concise and non-scary. Rephrasing this to: "Tell us what happened and how long ago" would be as concise and already much more useful. The toughest issues are the ones difficult to reproduce so they are not "happening".
,
May 31 2018
,
Jun 7 2018
Why don't we just add a timestamp field to the logs?
,
Jun 7 2018
#10 the logs have already plenty of timestamps. The issue here is how to encourage the user to let us know when the problem happened (if there was a specific time), since the time of filing feedback could be arbitrarily far from that time, and without that information we can spend a lot of time looking at various events and how they correlate.
,
Jun 7 2018
This is of course, fairly trivial to implement - but we need PM/UX to look at this and tell us what the field/language should look like (or even if this is an acceptable field to add).
,
Jun 7 2018
(Changing title to more clearly reflect what is being asked for) |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by yungleem@google.com
, Jan 9 2018