Tickets showing up after index

[Ryan L]

Hello, 

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. 

[Aggeliki K]

Hello @Ryan L and @Earl McCutcheon ,

I just had the same issue with tickets that were somehow created after re-indexing was performed.

Re-indexing completed with success but these new issues were created with an old creation date.

I checked the workflow as @Earl McCutcheon suggests and I can see that the post function about re-indexing exists. 

While trying to figure out what has cause this creation, I bumped into your question.

Have you found anything about this case?

Thank you in advance,

Aggeliki

[Earl McCutcheon]

Hi @Aggeliki K ,

This is going to be on a case-by-case basis as there are a lot of moving parts that could contribute, it could be coming from a configuration issue or a bug and more details on the actions that lead to the cause as well as reproduction steps are going to be needed to narrow it down,  so the best thing to do is systematically start digging for more information on what is happening in the background.

I recommend starting off in the log files, referencing the following for a good starting point of where to look:

• https://confluence.atlassian.com/jirakb/useful-log-files-in-jira-1027120387.html

And see if you can spot any index-related errors, first without debugging enabled then move on to enabling the debug levels as described in the Troubleshoot index problems in Jira server KB mentioned before.

Hope this helps get you on the right track and if you do find anything please share it here as it helps out a lot in case another user runs into something similar in the future.

Regards,
Earl

[Aggeliki K]

Hello @Earl McCutcheon ,

Thank you for the information.

I will come back with any questions or foundings.

Regards,

Aggeliki

[Earl McCutcheon]

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:

• Troubleshoot index problems in Jira server

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:

 

Regards,
Earl