Pivot report displays shifted period

Issue #1175 open
Alex Kiselev _Itransition_ created an issue

We are on jira 7.5.0 and Timesheet plugin 3.0.8.7

System timezone is Europe/Minsk

There are users with different timezones. We are know about https://www.jiratimesheet.com/wiki/Multiple_Time_Zones.html and described behaiour is fine for us.

But when user with timezone America/Denver builds Pivot report for project and selects period from 1/Sep/17 to 30/Sep/17 - report displays dates from 31/Aug/17 to 29/Sep/17.

We expect that report will display dates from 1/Sep/17 to 30/Sep/17.

Thanks in advance.

Comments (9)

  1. Alex Kiselev _Itransition_ reporter

    Hello, Andriy

    Thanks for your reply. But seems I still need your help and assistance.

    I have tried to add following JVM option in setenv.sh: first time: -Duser.timezone=Europe/Moscow and after: -Duser.timezone=Etc/GMT-3

    jira displays it correct in Administration -> System -> General options: System default: (GMT+03:00) GMT+3

    But the problem still exists: when user with timezone America/Denver builds Pivot report and selects period from 1/Sep/17 to 30/Sep/17 - report displays dates from 31/Aug/17 to 29/Sep/17. (URL is correct: ../ConfigureReport.jspa?startDate=1%2FSep%2F17&endDate=30%2FSep%2F17/..)

    Could you provide me with instructions how to solve the problem please.

    Thanks in advance. Alex

  2. Andriy Zhdanov

    Hi Alex,

    I afraid that Moscow may have similar problem, they have changed rules of time shifts. In issue I've referenced, there is Kalliningrad is recommended. Also you seem have had this problem already, see issue#455

    Again, the problem does not happen to me with the timezone settings you have, but I have latest JDK.

    Thank you.

  3. Alex Kiselev _Itransition_ reporter

    sorry - it's not clear to me yet - is there any solution or workaround to this?

    we have: java version "1.8.0_102" Java(TM) SE Runtime Environment (build 1.8.0_102-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)

  4. Alex Kiselev _Itransition_ reporter
    • changed status to open

    Andriy, hello. Sorry, I don't understand why you have changed state to Resolved - we still have problem and we don't have any fix (or even workaround)

    Problem #466 and #455 are looked similar but if you see the reason of the problem is in JDK and timezones Minsk|Moskow - it should work fine for GMT+3.

    We don't have even behaviour like described here https://bitbucket.org/azhdanov/jiratimesheet/issues/466/time-sheet-report#comment-13617775.

    It's still the problem for us. Hope you'll help. Thanks in advance. Alex.

  5. Log in to comment