Jira jql query for worklogdate does give wrong result after upgrade from 8.x to 9.4.3

[eeas_bekl]

Hi, 

After upgrading from Jira 8.x to 9.4.3 i get wrong results for my jql queries depending worklogDate. 

For example: 

worklogDate >= "2022/01/01" AND worklogDate < "2022/02/01" or

worklogDate >= 2022-01-01" AND worklogDate < 2022-02-01

Before the upgrade i received the tickets where work was logged within this time range correct. There was like 60 issues i got. Now after upgrade i do the same query and receive just 44 issues. When i double check it i saw that some issues are missing!

Doing a database query or checking the issues one by one i can see the worklog so it is there for sure, just the query gives me wrong results. 

I did not find any known bug and i was not able to raise one. So my question: Does someone have similar issues and maybe a workaround or a fix? 

I have already tried reindexing. 

Antoerh question (not that important but also interessting): 

Doing the jql with worklogDate in lower case "worklogdate" gives me completly different results which are even wrong (i.e. there is no a time logged there). Is this normal?

Thanks in advance

Best regards

[eeas_bekl · Accepted solution]

For anyone else haveing similar issues checkout the safeguards settings. 

My issue got solved after chaning the default value (100) for jira.safeguards.indexing.issue.worklogs to 5000 within the setenv.sh

Here are also some helpful links: 

https://community.atlassian.com/t5/Data-Center-articles/Introducing-Safeguards-for-Jira-index/ba-p/2037880#M433 

https://confluence.atlassian.com/jirakb/what-s-changed-in-jira-after-the-implementation-of-indexing-limits-1131089687.html 

https://confluence.atlassian.com/jirakb/introducing-safeguards-to-jira-index-1131089657.html