Timesheet Report & Gadget generates Timeout error

[John Fisher]

We currently run the existing timesheet report across the team (around 30+ people) for a couple of weeks for internal reporting. The new report or gadget never returns any results and generates the following timeout error:

Based on the current

We are using the Cloud version which is reporting as 1.1.5 in the add-on.

[Andriy Zhdanov]

Hi John,

Thank you for reporting the problem. I've just made small change, to load issues by 100, instead of maximum possible 1000, basing on the following article: https://confluence.atlassian.com/display/JIRAKB/Changing+maxResults+Parameter+for+JIRA+REST+API

Could you please let me know if it makes any difference?

Thank you.

[John Fisher]

I am still experiencing the timeout error the same as originally logged but in addition I am now sporadically receiving a "NO DATA" message in the body of the report.

[Andriy Zhdanov]

Issue #761 was marked as a duplicate of this issue.

[Andriy Zhdanov]

Hi John,

Could you please try it again - I've added some improvements (particularly, reduced data loaded from JIRA).

Thank you.

[John Fisher]

I've finally got the reports producing results (it takes a very long time to render) for a 2 week period. It seems the Pie Chart can handle greater date ranges without timing out. Now that I have some results I try and download the worklog to excel (after all the whole point of generating the report) in Edge it takes me to a blank page with no URL, does nothing in Chrome and in IE it just takes me to a blank screen with a huge URL as follows:

data:application/vnd.ms-excel;charset=utf-8;filename=exportData.xls;base64,PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4bWxuczp4PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpleGNlbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1odG1sNDAiPgo8bWV0YSBodHRwLWVxdWl2PSJjb250ZW50LXR5cGUiIGNvbnRlbnQ9ImFwcGxpY2F0aW9uL3ZuZC5tcy1leGNlbDsgY2hhcnNldD11dGYtOCI+PGhlYWQ+CjwhLS1baWYgZ3RlIG1zbyA5XT4KPHhtbD4KPHg6RXhjZWxXb3JrYm9vaz48eDpFeGNlbFdvcmtzaGVldHM+PHg6RXhjZWxXb3Jrc2hlZXQ+PHg6TmFtZT57d29ya3NoZWV0fTwveDpOYW1lPjx4OldvcmtzaGVldE9wdGlvbnM+PHg6RGlzcGxheUdyaWRsaW5lcy8+PC94OldvcmtzaGVldE9wdGlvbnM+PC94OkV4Y2VsV29ya3NoZWV0PjwveDpFeGNlbFdvcmtzaGVldHM+PC94OkV4Y2VsV29ya2Jvb2s+CjwveG1sPgo8IVtlbmRpZl0tLT4KPC9oZWFkPgo8Ym9keT4KPHN0eWxlPgo8IS0tYnIKICAgIHttc28tZGF0YS1wbGFjZW1lbnQ6c2FtZS1jZWxsO30KPCEtLXRhYmxlCiAgICB7bXNvLWRpc3BsYXllZC1kZWNpbWFsLXNlcGFyYXRvcjoiXC4iOwogICAgbXNvLWRpc3BsYXllZC10aG91c2FuZC1zZXBhcmF0b3I6IlwsIjt9Ci0tPgo8L3N0eWxlPgo8dGFibGU+CiAgPHRyPgogICAgPHRkPlByb2plY3Q8L3RkPgogICAgPHRkPlR5cGU8L3RkPgogICAgPHRkPktleTwvdGQ+CiAgICA8dGQ+VGl0bGU8L3RkPgogICAgPHRkPkNyZWF0ZWQ8L3RkPgogICAgPHRkPlN0YXJ0ZWQ8L3RkPgogICAgPHRkPlVzZXJuYW1lPC90ZD4KICAgIDx0ZD5EaXNwbGF5IE5hbWU8L3RkPgogICAgPHRkPlRpbWVzcGVudCAoaCk8L3RkPgogICAgPHRkPkNvbW1lbnQ8L3RkPgogIDwvdHI+CiAgPHRyPgogICAgPHRkPlImRCBPbmxpbmUgU2VydmljZXM8L3RkPgogICAgPHRkPkJ1ZzwvdGQ+CiAgICA8dGQ+T0xTLTEwMjI8L3RkPgogICAgPHRkPkVubGlnaHRlbmVkIEhhaXIgU3R1ZGlvIC0gVW5hYmxlIHRvIHN5bmMgVmVyOCBUaGlzIG1ldGhvZCBvciBwcm9wZXJ0eSBjYW5ub3QgYmUgY2FsbGVkIG9uIE51bGwgdmFsdWVzLjwvdGQ+CiAgICA8dGQ+MDIvMDkvMjAxNiAxMTo0OSBQTTwvdGQ+CiAgICA8dGQ+MDIvMDkvMjAxNiAxMjowMCBBTTwvdGQ+CiAgICA8dGQ+dmlyYWxwYW48L3RkPgogICAgPHRkPlZpcmFsIFBhbmR5YTwvdGQ+CiAgICA8dGQ+NS44MzwvdGQ+CiAgICA8dGQ+LSBQcm9ibGVtIHVuZGVyc3RhbmRpbmcuCi0gU3RhcnQgd2l0aCBJbnZlc3RpZ2F0aW9uIGF0IGNvZGUgbGV2ZWwgZm9yIHJvb3QgY2F1c2UuPC90ZD4KICA8L3RyPgogIDx0cj4KICAgIDx0ZD5SJkQgT25saW5lIFNlcnZpY2VzPC90ZD4KICAgIDx0ZD5FcGljPC90ZD4KICAgIDx0ZD5PTFMtMTAzMDwvdGQ+CiAgICA8dGQ+T0xTIC0gT25saW5lIFdhaXZlciwgQ3VzdG9taXNhYmxlIEZvcm1zLCBQaG90byAoVUsgQVUgUmVxdWVzdCk8L3RkPgogICAgPHRkPjAyLzAzLzIwMTYgMTA6MTkg

[Andriy Zhdanov]

Hi John,

It looks like your browser is not able to recognise it as downloadable for some reason. According to wikipedia all browsers support it.

Thank you.

[Andriy Zhdanov]

I assume timeout problem is resolved.

[John Fisher]

I have done further testing to expand my reporting window and still receive the Timeout problem. To give you an idea of volume, I am trying to report on just over 300 issues resulting in 940 worklog entries across 2 weeks. The current Timesheet report generates an output in a couple of seconds.

I have logged the Excel export as a separate issue.

[John Fisher]

Further testing shows that all reports return results (very very very slow to render in IE) but the Pivot by Statuses generates a Timeout.

[Andriy Zhdanov]

Pivot By Status timeout seems to me a minor problem, that can be fixed later, depending on https://jira.atlassian.com/browse/JRA-59998

[Andriy Zhdanov]

Moved to azhdanov/timerepots