Bug #284
openchanging a user's timezone hides reports
0%
Description
reports are 1:1 with timeframes, which have timestamp boundaries based on the user's timezone.
If the user changes timezones, then attempting to load a report results in looking for a timeframe with start and end times that no longer match, and so a new report is created.
Fixing this requires some careful consideration; maybe convert all present and future reports to the new timezone? but then the boundaries aren't precise for longer ones like month or season, they'll be off by whatever the timezone offset difference between the new and old timezones is.
manually adjust the end times of current reports, and then new ones get created with the new timezone? more complex put it could work, and would match the user expectation. the day/week/month/season/year gets longer by a few hours if you go west and stay there.
Maybe when changing the timezone, which should require user confirmation of all this, should ensure that all current timeframes and reports are created, manually fudge the end time based off of the new timezone, and then newly created timeframes would be in the new timezone?
Man this is super complicated. It may even be worth it to just remove this functionality and force the user to set their one and only timezone in the user registration dialog with a notice that this can't be changed. Much simpler fix and who really moves anyways? not me.