nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Missing worklogs on API call

emanuel.borsoi

I am using the following query to get data from the api:

/rest/api/3/search?jql=worklogDate+>%3D+"2025-02-01"+AND+worklogDate+<%3D+"2025-02-28"&fields=key,summary,worklog,project&expand=worklog

It works, I get the needed data, except of one single issue where I get the logs up to a certain date, all later logs are skipped. Later logs of other issues are returned.

Any idea why?

Accepted answers

David Nickell

It's a feature, not a bug :-)....

I don't know if I ever saw it documented, but I have experienced the same thing. When you pull back Worklogs (or changelogs too) when you are doing an issue retrieval, you only get a certain number if worklogs (and I'm guessing the root cause is worklog pagination).

I don't know if it will matter if you try to pass "limit" querystring value into your call, but you will still eventually have to deal with Pagination.

So, when I need worklogs, I walk my issues list and go get the worklogs (and paginate).

All comments

David Nickell

It's a feature, not a bug :-)....

I don't know if it will matter if you try to pass "limit" querystring value into your call, but you will still eventually have to deal with Pagination.

So, when I need worklogs, I walk my issues list and go get the worklogs (and paginate).

Anton from JetHeads_io

Hey @emanuel.borsoi! 👋

We’ve actually run into similar issues while building JetTime — Jira doesn’t always behave consistently when it comes to time zones. Even when using correct JQL, some worklogs outside the expected date range can be skipped or appear missing.

To work around this, we always extend the date range by 24 hours both before and after the target period, then filter the worklogs precisely in our scripts. That extra buffer helps ensure you’re not missing logs due to timezone quirks or edge cases.

You might want to give our app JetTime a try — it uses this approach under the hood, and you can compare its results with yours. It’s free during the trial and stays free forever if you have under 10 Jira users.

— Anton, from JetTime

emanuel.borsoi

Hi,

indeed, after some tests I noticed that the maximal number of returned worklog attached to an issue is 20, chat GPT confirmed this feature.

So my solution was to load all issues with worklogs falling in a particular range and then for all issues load recursively all worklogs.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud