Not sure if this is worth the effort as dealing with timezones would significantly increase complexity in general since the entire app is based around time tracking.
The issue stems around the fact that if you track an entry in one timezone, then change timezones and view the data and the times will appear to be off even though they are correct for the current timezone.
I'm not sure if it's worth it to keep entries timezone specific so the data is displayed consistently at all times (because dealing with timezones is a PITA because of how many contingencies there are).
This is untested, but what happens if you start in one timezone and stop in another?
Will likely just enforce that all entries will be made in a user specified timezone, instead of making it a piece of data on a history entry (will just a user setting taken into account when displaying data).
Will likely need to use UTC time if not already. Something to look into.
Not sure if this is worth the effort as dealing with timezones would significantly increase complexity in general since the entire app is based around time tracking.
The issue stems around the fact that if you track an entry in one timezone, then change timezones and view the data and the times will appear to be off even though they are correct for the current timezone.
I'm not sure if it's worth it to keep entries timezone specific so the data is displayed consistently at all times (because dealing with timezones is a PITA because of how many contingencies there are).
This is untested, but what happens if you start in one timezone and stop in another?
Will likely just enforce that all entries will be made in a user specified timezone, instead of making it a piece of data on a history entry (will just a user setting taken into account when displaying data).
Will likely need to use UTC time if not already. Something to look into.