Hello, I am using the Jira REST API for retrieving the most recent (in the past month) worklogs of a project. I use the "../rest/api/latest/search?fields=worklog&jql=worklogDate%20%3E%3D%20%27.." endpoint, in which I specify JQL to retrieve worklogs after a specific worklog date and for a specific worklog author. I have an issue with one specific ticket (which is a task) that has valid worklogs on it which are shown in Jira, but when using the API, it doesn't return all worklogs, more specifically it doesn't return the worklogs after the 20th of July. This is specific only to this ticket, as every other ticket that has worklogs for the past month in the project is being correctly returned by the Jira API (and all the returned tickets are from a single request to the endpoint shown earlier including the 'broken' ticket). The specific ticket that is not being returned by the Jira API is a task, around two months old and I see nothing wrong with it compared to other tickets. I tried to log in older tickets for some random day in the past month and is being correctly returned as well by the Jira API, so it's not because of the age of the ticket. Has anyone seen such an issue and is there some solution and logical explanation for it? I hope that it does not happen to another random ticket in the future.
I ran into something similar. Apparently there is a known bug in the API that limits the number of worklogs returned to 20 per issue. A bug was opened 5 or 6 years ago and has never been addressed. The only workaround I'm aware of is to check the worklog fild in the API response too see if "total" is > 20. If so, use the Get Issue Worklogs API for the issue in question. This call will return all worklogs for the specified issue.
Hello @Ivelin Tsanev ,
Welcome to the community!
I hope you are doing well!
Reading your concern I suspected that it be related with the worklog permission however with another statement that you shared that it can only be observed with a specific issue not all. I don't think it is a permission related problem. My suggestion would be to raise a issue to support to check the project and issue related configuration thoroughly to understand the cause of the behaviour.
Please raise a support issue on :https://support.atlassian.com/contact/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, thanks for the welcome and advice, I raised a support ticket and received some useful feedback!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.