1. Tempo Avatar Tempo
  2. Prime
  3. servertimesheet
  4. Issues

Timesheet Date Range

Issue #1072 resolved
Eric Vennard created an issue

When i try to execute report for 1st day in month to last day in month it actually generates for start date -1 and end date -1.

Comments (32)

  1. Andriy Zhdanov

    Hi Eric,

    Could you please add (obfuscated) screen shot and browser url for the report?

    Thank you.

  2. Eric Vennard reporter

    http://**/secure/ConfigureReport.jspa?startDate=01%2FFeb%2F17&endDate=28%2FFeb%2F17&targetUser=&targetGroup=&excludeTargetGroup=&projectRoleId=&projectid=16708&filterid=&priority=&sum=&sumSubTasks=true&groupByField=customfield_16506&collapseFieldGroups=true&moreFields=&selectedProjectId=16708&reportKey=jira-timesheet-plugin%3Areport&Next=Next

  3. Andriy Zhdanov

    Could you please clarify what timezone are you in? And could please check if it's the same problem, say for January? And also exact plugin version.

  6. Andriy Zhdanov

    Hi Eric,

    Could you please clarify plugin version?

    And please check also you have correct time zone settings in your JIRA profile.

    Thank you.

  7. Eric Vennard reporter

    Hi Andriy

    Version installed is 3.0.5.2.

    My time zone profile is GMT. What defines a 'correct' time zone?

    Thanks Eric

  8. Andriy Zhdanov

    Hi Eric,

    Would it be possible for you to try if problem reproduces on latest version 3.0.7.8?

    By correct time zone, I meant that it corresponds to what you have indeed, i.e. GMT.

    Thank you.

  9. Eric Vennard reporter

    Hi

    Upgrade and still happening. When i set date params and then go back to re-configure they have junped back by 1 day also.

    For example, executed for 01/01/17 to 31/01/17: * Report shows 31/12/16 to 30/01/17 (d -1) * Select Configure again and dates I previously added now show 31/12/16 and 30/01/17 in their respective text boxes.

    Thanks Eric

  12. Andriy Zhdanov

    Hi Eric,

    I've tried with exact timezone settings and all worked fine for me.

    I have seen similar problem already, in issue#466 with GMT+3, in Russia, caused by frequent DST changes so that Java did not support it properly. Workaround was to use different timezone with the same offset. You can try changing timezone in your profile to Lisbon, for example. If it helps, then updating java on JIRA Server might be real solution for this.

    Alternatively, you may try not to chose dates, but check Month View option in report parameters.

    Finally, stupid, but unless anything else works, just select next day in the options.

    Thank you.

  14. Eric Vennard reporter

    When i try to use Month View and SumTasks it shows processing but then reverts back to parameter selection. Basically it does not work. Screenshot attached.

  17. Andriy Zhdanov
    • changed status to open

    Hi Eric,

    May be you need to adjust Number of Weeks also, because using Month View it corresponds to months, and there is limit for maximum period.

    Thank you.

  18. Eric Vennard reporter

    Hi

    I am JIRA admin and global value for max. period is 180. I have attached screenshot of all parmeters set. It thinks about it and then returns me to the exact same screen. No errors et.

    -Eric

  21. Eric Vennard reporter

    No errors. Returns after exactly 1 min each time so may be timing out due to volume of data or calculations? Works fine without SumSubTasks but I need this to aggregate up the values.

  22. Andriy Zhdanov

    That's strange that it opens gadget configuration screen actually.

    What if you save configuration with no Sum Sub-Tasks, and click Details to get into report, then click change and check Sum Sub-Tasks there. See if gives any error.

    Thank you.

  26. Eric Vennard reporter

    Same result. At both gadget and detail level. Did it for March only so data being returned is minimal. I am using a Custom Field to Group By. Maybe SumTasks doesn't like this?

  29. Andriy Zhdanov

    Sorry, is there any case it works at all? It used to work without Month View, but does it still work? May be some other parameters has changed since it worked?

  30. Eric Vennard reporter

    Seems as if this happens once the query runs over 60 secs. Summing sub tasks maybe extends the query as more aggregation happening. I will see if I can increase default session timeout to see if it helps.

    Once is does hit 60 secs the add in behaves strangely and thus it has been hard to even come to this assumption.

  31. Andriy Zhdanov

    Oh, that's good observation. I did not expect this is possible in JIRA, you might have some custom session timeout handler.

  33. Log in to comment
Assignee
–
Type
bug
Priority
major
Status
resolved
Component
–
Version
2.9
Votes
0
Watchers
1