Lucene health check failing & issues created with no type assigned

[Jack Moran]

Hi,
Currently in our Jira instance we have 5 'sub tasks' created which have somehow ended up without an issue type.
Once we noticed them, we restarted the server and this has caused the lucene health check to fail.

We cannot delete these issues as no one has permission to do anything with them.

Any suggestions on how we could delete these issues?

Thanks in advance

[Nic Brough -Adaptavist-]

I can only think of one way you could get into this state, and if I'm right about it, then I would very strongly recommend removing all but the jira user access to the database and giving that one account a new password, then sacking anyone who asks for their database access to be restored.

To fix the problem, you will need database access though. 

• Go to the AT project and look at the list of available issue types. 
• Stop Jira and take a backup
• Go into the database and look through the issuetype table for any parent-level issue type that the project uses. 
• Once you have that ID, you can go to the jiraissue table and change the issue type on each of the five broken issues to it.
• Restart Jira
• Re-index the project
• Run the integrity checker and let it correct anything it finds
• Now delete the issues if you want rid of them

[Jack Moran]

Hi Nic,
Thanks so much for that!

In terms of it being another user, we are sure it was not as it happened to 5 issues I was creating at the time via the UI.

We think a plugin is causing sub tasks to not be created correctly, as they take a few minutes per sub task (that's what I was testing) and the modal doesn't close after they are created.

I then tried to use our bulk add sub tasks plugin, which created some successfully but then the server started messing up. We restarted Jira, and my theory is that it has restarted partway through adding these sub tasks and it has corrupted them.

Next job is to try and figure out which plugin is causing all this!

Again, thanks for the help.

Jack