3 ms·
This sounds normal and not specific to Japan.
by sanxiyn 7y ago
This sounds normal and not specific to Japan.
- philliphaydon 7y ago14 years in this career and Japan is the only country I've had to do this with.
- coldtea 7y agoHave you changed timezone storage and displayed dates wrong (even if it was a configuration issue) in many other countries/customers?
- philliphaydon 7y agoAll dates stored in UTC, so if any other country raised a ticket, we just told them to update their timezone in their profile, and the client was happy. Japan is the only country that this required incident reports.
- netsharc 7y agoSounds like a pain in the ass. I would just build the incident report form to have the option "Date/times are all wrong", and when you see the user is from Japan and selects this drop down option, check if their timezone is set correctly, and if not, reset it to JST... Then the form would prompt them "Are you sure, please look again", and most of the time the problem will have disappeared, right?
- duxup 7y agoI've worked with Japanese customers. What he described is quite unique to Japan, particularly how many completely run of the mill situations (hey how does this widget work) go on for weeks of expiation. I'm talking about even completely predictable things. Like "Hey if I turn this thing off, is it off?" will start weeks long series of questions. I don't fully understand it, but it is a Japanese thing for sure.