Worklog report working but missing a lot of data

[reubenbubu]

Checklist before you being

• I am sure that I am already using latest version of Jira Assistant
• I had verified that, no similar issues are already reported in issue tracker
• I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
• I had verified that, my query is not answered in FAQ section of website
• I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Jira cloud App

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Cloud Jira

Version of Jira Assistant

Web

What browser are you using?

Chrome

What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.

Windows

Bug Description

I am trying to load a worklog report for a whole month for a big team. The report loads but is missing a lot of data.

I managed to track down the source of the issue, when Jira Assistant initially queries for all the tasks containing the worklogs it sets maxResults=1000, however JIRA seems to be ignoring this and only returns 100 tasks with a nextPageToken.

I made it work my doing the API requests myself and building an array of all the tasks. Then i set a breakpoint in index.js as seen in the image and pushing the task array into e.issues and then continuing the execution.

In brief if you follow the pagination of the initial request to get all the tasks this issue should be resolved.

Checklist before you submit

• I have ensured not to paste any confidential information like Jira url, Mail id, etc.
• I have verified my browser console logs and added necessary details (if required)
• I have added required screenshots if the bug is related to UI (as necessary)

[github-actions]

Hi @reubenbubu, thank you for reporting this issue regarding the worklog report missing data. It appears that your experience aligns with several previous reports, particularly the behavior surrounding the maxResults limit in API calls. Similar issues have been explored in tickets like #15, where users have noted the limitation of the API response to 100 tasks despite requests for more. Your suggestion about following pagination to retrieve all tasks is crucial and will be taken into account for enhancements. I'd encourage you to keep monitoring for updates related to these discussions in the existing tickets.

---

Disclaimer: Please note that this response has been generated automatically by an AI bot. While we strive for accuracy, there may be instances where the information is incorrect or inappropriate. We review these responses periodically and will make necessary corrections as needed. We appreciate your understanding.

[shridhar-tl]

@reubenbubu - I have done the changes and pushed the changes to all the web store. While Chrome and Firefox has already published the changes, Edge Web Store is still reviewing the changes. It usually takes 5 - 7 working days for the review to complete.

Can you please validate the fix and confirm if it is working fine for you. I do not have data to validate this fix and hence requesting the users to confirm if the fix works. You can update your chrome version manually by going to chrome://extension and enable dev mode and click on update button.

Then let me know if its working fine for you now. I am closing this ticket as of now for me to manage the tickets. If it is still not resolved, please reopen this ticket.

[giamma]

Hi, the problem is still present at least when using Jira for Data Center.
According to the API documentation, the response of the service returning the worklogs (rest/api/2/issue/${issuekey}/worklog) for a issue begins with:

{
  "startAt": 0,
  "maxResults": 1000,
  "total": 3567,
  "worklogs": [
    {

where total is the total number of worklogs for the issue and maxResults is the number of worklogs returned in this call.
If total > maxResults you have to make another call setting as the initial offset the maxResults of the previous call.

In pseudo code:

 offset = 0;
 pageSize = 100;
DO
  response = getJiraWorklogsForIssue(key, offset, pageSize);
  // accumulate the worklog in the result collection
  result.add( response.getWorklogs() );
  total = response.getTotal();
  offset = offset + result.size();
WHILE (offset < total)