Some custom fields were deleted in JIRA but there were still in the behaviour-plugin. At the beginning, the behaviour was mapped to all issue types. If the behaviour mapping is changed, the indexing fails and the logs indicate that the deleted fields cannot be found. This is the error log i get:
[onresolve.jira.groovy.Behaviour] Could not find field with key: customfield_10002
As a troubleshoot, I tried to delete the fields in the behaviour plugin as well but it did not help. The JIRA version is v6.1.4#6159-sha1:44eaede. The behaviour plugin version is 0.5.10. The script runner version is 2.1.16.
Actually, I found out that 2 other behaviours contained the deleted fields. I delete the fields in the behaviors, and reindex but I got another error message in the logs: [atlassian.jira.index.AccumulatingResultBuilder] java.util.concurrent.ExecutionException: java.lang.NullPointerException: Cannot invoke method getValidators() on null object
Also check if you are using any "Hideable" custom field types, I don't think anything else could cause this problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you create an issue at https://jamieechlin.atlassian.net/browse/JBHV including the full stack trace please?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I turned the behaviour plugin down, then I reindexed and it worked. After this, I turned on the behaviour plugin, deleted the fields which have been deleted in the behaviour and after this, the inexing is still failing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But after indexing turn it on again, and then delete the fields from the behaviours that have been deleted...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jamie, thanks for your quick answer. I disabled the behaviour plugin under "Add-ons", Manage add-ons". And then the indexing works but it's not an option for me since I'm using other behaviours. If I unmap the behaviour which is causing problems the indexing fails as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try disabling the plugin then reindexing. I think this can only happen with hidden field types
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.