nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

jira is not indexing properly.

Sreenivasaraju P

hi,

We are using Jira 5.1. We are facing some problem frecquently.

The status of some particular requests are showing differently in the issue navigator and in issue.

ex : JIRA-123 status is showing as STATUS A in the navigator ,but if we go the ticket, it is showing STATUS B(which is correct).

If we do re-indexing , then the status is showing correctly(STATUS in the issue navigator also.

Any idea on this.

Accepted answers

Nic Brough -Adaptavist-

So far, you've had two different answers. They are both correct, and complementary, but to be clear, what's going on is:

1. Something is corrupting your index (you say "We are using Jira 5.1. We are facing some problem frecquently." so it's not a one-off). See Renjith's answer

2. Once the index is damaged, you are seeing problems.

You need to fix both of these. Re-indexing and clearing the caches will repair the damage. But they won't fix the root cause. You need to identify what is causing the damage and fix that, otherwise it will simply continue to corrupt your index, and you'll need to keep repairing it.

All comments

Renjith Pillai

Which means that you are modifying the issue either in plugins, script runner post functions, listeners etc. and not doing the step for individual issue reindex.

Mizan

May be the indexes have got corrupted .

Folllow the below steps:

Stop JIRA , delete the indexes directory under JIRA_HOME/caches/ then restart JIRA .

This most probably might solve the issue .

AhmadDanial

Hey there, prathighantam.

As mentioned by Mizan earlier on, clearing your JIRA caches might help. What I would propose is a complete clean up of your JIRA instance as per the following:

Shutdown JIRA instance
Delete the contents of the JIRA Home Directory\plugins\.osgi-plugins directory
Delete the contents of the JIRA Home Directory\plugins\.bundled-plugins directory
Delete the contents of the JIRA Installation Directory\work directory
Restart JIRA instance
Try to perform the re-indexing

Hope it helps.

Warm regards,

Danial

Daniel Garcia12

I suggest you do the following:

1.- Stop Jira.

2.- Delete folder 'cache' in Jira Home.

3.- Start Jira.

4.- Reindex again (administration menu)

Hope it helps!

Daniel

Nic Brough -Adaptavist-

So far, you've had two different answers. They are both correct, and complementary, but to be clear, what's going on is:

1. Something is corrupting your index (you say "We are using Jira 5.1. We are facing some problem frecquently." so it's not a one-off). See Renjith's answer

2. Once the index is damaged, you are seeing problems.

Mizan

Hi Nic ,

Can such issue occur after upgrading JIRA ? for us this use to happen after editing the issue .

Nic Brough -Adaptavist-

An upgrade will perform a re-index as part of the process. I'd expect a vanilla installation of Jira to be absolutely fine after upgrading.

Adding/upgrading plugins afterwards may cause problems, but that depends entirely on them and your system. The worst case is that you should allow time for a second re-indexing run after an upgrade.

However, an upgrade is only one possibility of a root-cause, and if you've re-indexed after it, then you should not be seeing any index issues. If you are getting them after re-indexing, then something else is doing the damage.

Mizan

Thanks Nic ,

I am facing this same issue , I deleted the indexes folder but the issue still persisit , can you please help me in finding the root cause for this ? What can be the probable cause for this ?

I checked the post functions and the issues are reindexed .

Sreenivasaraju P

Yes ,we are using issueManager.updateIssue() in our post functions, it is causing problem

Sameer Kinra

Works like a charm, and we did the this step 1st though, stop JIRA delete the indexes directory under JIRA_HOME/caches/ then do step 2 from your instructions.

Jordan Packer_8ftolu

I seem to be experiencing something similar.... I'm updating some custom fields in a scripted listener, and ever since I started testing heavily with it our environment has been running into indexing and database corruption issues. What's the recommended way to make custom field updates in a scripted listener so that we don't run into these problems?

Salome Khaindrava

Chack known problems with 3rd party apps - https://confluence.atlassian.com/jirakb/known-major-problems-with-3rd-party-apps-in-jira-946618564.html

We had the same problem and the cause was plugin META-INF KFT - Email This Issue.

We disabled it and the problem was fixed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira