ScriptRunner parent issue field indexing error

[G]

Hi,

I'm using the script runner's parent issue field  to generate a parent issue such as a Feature or a Theme that goes above Epic. The script works correctly and there are no failures but it is giving indexing errors continuously for all the parent issue field. 

The fields are only contexted for 2 projects and not globally but the error appears on all issues.

Below is one of the error:

/secure/AssignIssue.jspa [c.a.j.issue.index.DefaultIssueDocumentFactory] Error indexing issue JIRADEMO-377: Dropped: [customfield_16008, customfield_16106, customfield_16107]

In this case the field is not even available for the JIRADEMO project,

The searcher I'm using for these fields is the Issue Key Searcher although it does not accept  the below search:

"Feature Issue" is not EMPTY

It will say 'The operator 'is not' is not supported by the 'Feature Issue' field.'

I'm on Jira 7.2.4 and ScriptRunner 5.2.1. 

Is this a bug or is there something not done correctly in the set-up?

Cheers,

Gaj

[G · Accepted solution]

After seeking support from Adaptavist, they can reproduce this error and have logged a bug on https://productsupport.adaptavist.com/browse/SRJIRA-2826 

[Andy Heinzer]

It's difficult to say exactly what causes this.  There is a KB here that might help, please see JIRA Indexing Operations Display Error indexing issue Dropping Custom Field.

All we know for sure right now is that Jira was not able to index the values of those three custom fields at that time.  And rather than fail the entire index, it decided to drop those values from the index attempt.

The KB explains that this usually happens on custom fields created by third party plugins.  It's not always a problem to see this.  As it appears in your situation, it sounds like things are still working correctly.  But I don't believe Jira will be able to resolve this error.   Perhaps reaching out to the plugin vendor, Adaptavist, might be helpful to address this problem.

[G]

Thanks Andrew for getting back. Yes I've raised a support ticket with Adaptavist to look into this.

I'm aware it's not too much of an issue as most things are working correctly. The problem I noticed was that our  lock down indexing time went from about 2 hours to 6 hours so that's a cause for concern. I feel these errors coming out might be causing delays.  I'm sure if I disable script runner and ran it it would be only 2 hours to reindex. 

I will wait to hear back from Adaptavist and hopefully it's a bug they can resolve.

Cheers,

Gaj