Same Update, but it will not resolve the initial problem which is that worklogs above 1000 will not come through JQL .
Atlassian suggested :
-
Use JQL to discover recently active issues — reliable within the 1,000-worklog window.
-
For complete worklog history, use the REST API directly:
GET /rest/api/3/issue/{issueIdOrKey}/worklog(paginated) no search limit applies here.
This workflow is fundamentally flawed: if JQL omits the issue ID entirely during the first query because the last 1000 worklogs does not fall in the desired range, third-party apps and integrations have no way to identify which issues require subsequent API pagination.