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.

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

Display "Report generated on XYZ" with the date converted in website's timezone (instead of UTC) #9076

Open
mattab opened this issue Oct 22, 2015 · 3 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.

Comments

@mattab
Copy link
Member

mattab commented Oct 22, 2015

follows up #9075

Currently, datetime is displayed in UTC.

It would be better to display the datetime in the website timezone, as it can get confusing otherwise:

  • when I'm looking at 2014 data, it says "Report generated on Dec 31st 2014 (UTC)" which is confusing (it was generated on Jan 1st 2015 in the website timezone)
@mattab mattab added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Oct 22, 2015
mattab added a commit that referenced this issue Oct 22, 2015
it would be better to convert the datetime to website timezone #9076
@mattab mattab changed the title Display report generated time converted in website timezone (instead of UTC) Display "Report generated on XYZ" with the date converted in website's timezone (instead of UTC) Oct 22, 2015
@mattab
Copy link
Member Author

mattab commented Oct 22, 2015

Example of what it looks like in Piwik 2.15.0:

2015

@tsteur
Copy link
Member

tsteur commented Oct 26, 2015

I think ideally it would always say something like 1 hour ago, 10 minutes ago, 1 month 10 days ago, 1 year ago. On hover, if needed, it could say Jan 01 2015 00:04:01 in the website's timezone UTC+8, which is ... in your timezone (and ideally we would also show it in users current timezone when it is different).

Showing a date here is not really helpful, especially when UTC is different than the websites timezone which might be again different of the users timezone. One never knows which one is used and even when you know it, you have to do the math to convert it to your timezone etc.

With JavaScript we could update the time when hovering... eg by having a timestamp in the HTML attribute or so. This could be an angular directive. Whenever hovering it, it would update the time and say eg "5 minutes ago", then 5 minutes later when hovering again say "10 minutes ago"

@mattab mattab added this to the Mid term milestone Nov 26, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
@mattab mattab changed the title Display "Report generated on XYZ" with the date converted in website's timezone (instead of UTC) Display "Report generated on XYZ" with the date converted in website's timezone (instead of UTC) + Show the hour of the day Jan 30, 2023
@mattab mattab changed the title Display "Report generated on XYZ" with the date converted in website's timezone (instead of UTC) + Show the hour of the day Display "Report generated on XYZ" with the date converted in website's timezone (instead of UTC) Jan 30, 2023
@rcontiuk
Copy link

rcontiuk commented Sep 28, 2023

There is an issue with instances that have the default timezones set to countries way ahead of GMT, like Australia. It seems like reports generated before UTC 00:00 will show "report generated on {{date}}", which some users (in EU or US) will see a report from yesterdays date. If the report is generated after UTC00:00 then "Report generated {{hours}} ago" which is a much clearer option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.
Projects
None yet
Development

No branches or pull requests

3 participants