ikdekker
commented
5 years ago Just thought of an alternative; I am unsure if this is native to Jira, however, the Clockwork App offers a timesheet overview with an export option. This may prove convenient if the issue iteration does not offer enough performance.
The drawback of this is the method of exporting, which is quite understandably, the need for manual action.
Since my goal of this library is to support is exporting working hours of employees of the past month, before the ~fifth of the month, there should be at least two workdays in which this could take place. Not ideal, but a decent start perhaps.
As far as I have seen, there is no support for Jira's v3-api endpoint /worklogs/list. This is somewhat troublesome, as the workaround is to fetch all (yes ALL) issues and get their worklogs. These can be checked for the appropriate date range, and aggregated into a single total per issue. The accumulated values may be used (per user) to calculate the values that are required to create a timesheet of the requested time.
This workaround is significantly slower on Jira Projects containing many issues. At this time, this is not a problem for my personal use case, so the first version of this library will not contain any support for improvement of this problem. In a later stage, the call to the aforementioned worklogs API call might be added, or the used jira-rest-client library replaced.
Some benchmarks, with a Jira (cloud) instance with ~400 issues will be added in the comments of this thread. If the speeds are not up to par with expectations, the workaround will be added before the first release of this library.
note: expectations of the workaround methods should exceed performance of several minutes (perhaps > 5, I really just need the process to complete for now).