Hacker News Reader

Comment by EMM_386 | Hacker News Reader

> Why? The most important info was the time at which the error happened (which, for users who were on Windows, was in the bottom right of the screen).

Except it isn't in UTC and it doesn't show an offset.

Even if you stored the user's timezone, that doesn't mean that's where they were working from.

View on HN

oooh. you got them. Like figuring out which timezone the user was in is impossible. What if the user intentionally set their clock wrong to mess with support.

You are being silly.

No, the people requiring a screenshot to include the time instead of just asking the user for an ID and time of error are the ones being silly. Have you ever heard of log filtering?

Or, some users might have hidden the taskbar, or the clock. Or have several screens, and only one of them has the clock...

Most users don't customize anything, even something as trivial as that. Most corporate users may not be allowed to. I bet they never had to deal with any of these supposed gotchas.

Users that might customise their system a bit by digging into the settings are usually more inclined to give a detailed report in case they encounter a bug or have a general knowledge of what to look for when requested for some information in my team's experience. Sounds much more like an edge case.

True, but if the policy is to reject all cut screenshots... I'd rather add an "unless the ticket contains all the relevant information".

The user not being in the time zone we expected has been exactly the information we were missing to debug something more than once. “The logs say it was 10am but the screenshot says 11… what if we were mishandling timezones?”

Reply on news.ycombinator.com