On 7th of January i did a Re-index due to changes being made in some of the projects. New tickets with new numbers started showing up in several projects but with the dates showing the 1st, or back in December. None of these tickets showed up before the re-index.
So this bring up 2 main questions:
1) What can cause this to happen?
2) is there a way to check for this short of doing a re-index. Either a check in Jira or running an SQL report? I'm assuming that i would look for NULL key values but it's hard to test.
Hello @Ryan L ,
As the manual re-index got the issue to reappear it defiantly sounds like the search index got out of sync from the DB. So first off as there could be something index wise failing in the background causing it to have fallen out of sync, you can usually pick up errors in the logging giving an indications of what went wrong if this is the case. Check out the following KB article on troubleshooting indexing issue errors to get a base line on what to check for:
There are a lot of possibilities covered in that KB but let me know if you find anything in particular that you have questions about.
Alternatively there might be an issue in the projects workflow and an index post function event could be missing in the create issue step. Check the workflow that is in use for the issues that are showing up post re-index and make sure there is a post function to "Re-index an issue to keep indexes in sync with the database." as the second to last step in the create issue step like this:
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events