How Lucene JIRA Cache Works

In some cases, it is necessary to run a Reindex in Jira to solve some Tempo (and JIRA) problems. But how is the logic behind it? 

Basically, the  Jira index works with a third-party library created by Apache called Lucene and this could affect Dashboards, Issue Search, Reports, Boards, and other functionalities. Lucene is able to achieve fast search responses because, instead of searching the text directly, it searches an index instead.

There’s a few recommendations and also a few important things that it’s good to keep in mind when we talk about problems with the index, this could be caused by a few things like outdated cache files, corruption in the indexes or major adjustments in the instance that affects directly the caches and database. So it’s important to keep in mind that sometimes it’s necessary to run with a determined frequency this re-index in the instance to avoid problems like that. I cannot confirm how long you run it in your instance, but sometimes only 2 weeks is necessary to experience problems like that, not only with reports but slowness, outdated information.

To finish, if you did new configurations with permissions, edited workogs, add new users, changed team and a lot of other things, this could impact directly in the cached information and affect only specific information. And like I’ve said before, this is not a specific behavior to Tempo, is it related to anything that is stored in JIRA.

Also, is good to read the following documentation: https://confluence.atlassian.com/jirakb/understand-the-index-process-in-jira-server-776654790.html