[TIME-281] Timesheet timezones mismatch

Issue #281 resolved
Andriy Zhdanov created an issue

Timesheet can be considered wrong in multiple timezones case.

Consider two users logged worked done at the same time, but one in India, on Tuesday, and other in US, west coast, on Monday.

Jira will show worklog as if both entries were recorded at the same time for both users, on Monday or on Tuesday, depending on viewing user.

However from Timesheet it is expected:

1) When one in US looks at timesheet, he would see own time worked on Monday, and colleague from India worked time on Tuesday.

2) When other in India looks at timesheet, he would see own time on Tuesday, and colleague from US worked time on Monday.

That would correspond reality and allow correct time audit in teams distributed over multiple time zones.

See https://docs.google.com/document/d/1ss_e6S_lvIIo1MiX9WLJ5Umv7hZrcZWZOXBrQK_RRwY/edit for better explanation. It is attached also.

By azhdanov/Andrew Zhdanov on Mon, 3 Sep 2012 09:51:39 -0700

Comments (4)

  1. Andriy Zhdanov reporter

    Attached screen shots here also for easier lookup.

    By azhdanov on Mon, 3 Sep 2012 09:53:32 -0700

  2. Andriy Zhdanov reporter

    Committed revision 169494: timesheet for worked user timezone

    By azhdanov on Mon, 3 Sep 2012 10:10:10 -0700

  3. Andriy Zhdanov reporter

    Committed revision 169736: fix lost worklogs on end date.

    Report date range is using viewing user timezone. In attached example for Jutamat endDate is 10/Oct 23:59 GMT+7. however worklog records are selected in server timezone, which is GMT-5 in the case, so endDate is 10/Oct 11:59 (am), and Sandbox user logged his time afternoon apparently, so it's not included by filter.

    If using server timezone, viewing user would see extra records. E.g. records created by Jutamat user on 11/Oct morning, will be included within endDate < 10/Oct 23:59 GMT-5 = 11/Oct 11:59 GMT+7(am).

    Fix is to expand database filter with one day before and one day after, and then exclude worklogs out of actual range by date converted to target user timezone.

    By azhdanov on Sat, 13 Oct 2012 06:38:20 -0700

  4. Log in to comment