You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We were coming off of a full reindex of Jira datacenter.
When I use the "updated" field in the jql it only finds the issue when I do a manual search via "Run Now" (preview), and it shows in the log and does the subsequent transition.
But when I let it run automatically via cron expression, then it doesn't find the updated issue.
I have a feeling that something might be cached or some user context is missing when the job runs by itself or maybe you just can't use "updated" in a ScriptRunner job JQL query or this is exclusively a datacenter problem?
Edit: The user has full admin permissions in the project
I think I might have figured out why the job searches were not working. Still testing this in detail:
I think all jobs were essentially sharing a single cached SearcherContext, which is used to search the index, and the recent version of the search method didn't have a finally block with
Which means whenever a Job used the search method , it created a SearchContext that was never closed, and this old cached SearcherContext then gets reused by other jobs, and apparently it holds or references a cached version of the index.
The whole searcherContext opening was done to prevent this issue, where logs get flooded: