The problem is caused by Safeguards for Jira index indexing limits that were introduced in Jira 8.22.2: https://community.atlassian.com/t5/Data-Center-articles/Introducing-Safeguards-for-Jira-index/ba-p/2037880#M433.
To fix the problem set jira -Djira.safeguards.indexing.issue.worklogs in setenv.sh to MAX_WORKLOGS_YOU_HAVE_IN_ANY_ISSUE (I guess 50000 is sufficient for most real cases0 (index all worklogs) and run the full re-index. After that you can put jira.safeguards.indexing.issue.worklogs back to 100 or what is acceptable for your business scenarios.Kudos to https://community.atlassian.com/t5/Jira-Software-questions/Jira-jql-query-for-worklogdate-does-give-wrong-result-after/qaq-p/2288452 It’s recommended to add it to JVM_SUPPORT_RECOMMENDED_ARGS variable. Multi variables should be space separated.
...
Related links:
...