You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When logging time, the time at GitScrum's headquarters in Europe is used rather than the user's. For example, I logged time on a task for a couple hours this morning in the Eastern Time Zone. The start and end time are listed as 13:32 and 16:27. Several hours later, it is 1:22pm where I live.
This is a suggested enhancement. It would be better to have no timestamps at all and only show the duration of time worked than to have timestamps from an irrelevant time zone.
Ideally, the user could select their timezone from within GitScrum. This would account for cases when VPNs or proxy servers are used.
Context
Having accurate task timestamps would be useful to keep an eye on when team members are working on tasks. It would enable a more holistic project management approach.
The text was updated successfully, but these errors were encountered:
When logging time, the time at GitScrum's headquarters in Europe is used rather than the user's. For example, I logged time on a task for a couple hours this morning in the Eastern Time Zone. The start and end time are listed as 13:32 and 16:27. Several hours later, it is 1:22pm where I live.
This is a suggested enhancement. It would be better to have no timestamps at all and only show the duration of time worked than to have timestamps from an irrelevant time zone.
Ideally, the user could select their timezone from within GitScrum. This would account for cases when VPNs or proxy servers are used.
Context
Having accurate task timestamps would be useful to keep an eye on when team members are working on tasks. It would enable a more holistic project management approach.
The text was updated successfully, but these errors were encountered: