Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Segment "Server time - hour" is using UTC timezone #16563

Closed
mattab opened this issue Oct 12, 2020 · 2 comments
Closed

Segment "Server time - hour" is using UTC timezone #16563

mattab opened this issue Oct 12, 2020 · 2 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. duplicate For issues that already existed in our issue tracker and were reported previously. worksforme The issue cannot be reproduced and things work as intended.
Milestone
Backlog (Help wan...

Comments

@mattab
Copy link
Member

mattab commented Oct 12, 2020 •
edited

Seems that when we create a segment using the "Server time - hour" dimension, it does match visits using the UTC visit time (hour).

For example creating a segment matching visits from "server time - hour" = 6, it shows visits from 8PM (the website is configured in UTC+2).

Reproduced on demo:

Screenshot from 2020-10-13 12-58-52

Also reported by a customer

Suggested steps:

  • confirm it uses UTC always or maybe another time like the actual server time?
  • verify whether this applies to all "Server time" segments
  • decide whether we want to fix the issue, and convert the time in the website timezone. (Then maybe rename "Server time" to just "Time" or "Visit time")
  • (or alternatively, we could maybe rename the segment to UTC time instead of Server time. but this could be confusing as timezones conversions are hard for everyone)
@mattab mattab added Bug For errors / faults / flaws / inconsistencies etc. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. labels Oct 12, 2020
@tsteur tsteur added this to the Priority Backlog (Help wanted) milestone Oct 13, 2020
@sgiehl
Copy link
Member

sgiehl commented Jun 2, 2022

Was that one kind of fixed with #18956, or is anything left we should apply?

@mattab
Copy link
Member Author

mattab commented Jun 6, 2022

@sgiehl sounds good, as we've renamed the segments to mention UTC so i'll close this

@mattab mattab closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2022
@mattab mattab added duplicate For issues that already existed in our issue tracker and were reported previously. worksforme The issue cannot be reproduced and things work as intended. labels Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. duplicate For issues that already existed in our issue tracker and were reported previously. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
3 participants
@tsteur @mattab @sgiehl