upgraded to Jira version 8.2.2 indexing fails

[Francesco Mazza]

Jira was successfully upgraded to version 8.2.2 on 02/07/2019 at 7:25 AM
Power Database Field PRO Version: 4.8.0.2 
Since I upgraded to Jira version 8.2.2 we have this problem: Indexing fails with Reindex All FAILED error. The incriminated fields are custom fields with multiple value by App Power Database Fields PRO. for example this is a log file error line: 2019-07-03 14: 03: 49,533 JiraTaskExectionThread-2 WARN Admin 843x1451x1 1x3hhsb 128.1.1.199 /secure/admin/IndexReIndex!reindex.jspa [cajira.index.AccumulatingResultBuilder ]DocValuesField "customfield_10305" appears more than once in this document (only one value is allowed per field).

Furthermore, when creating an issue, if I select multiple values from the custom field, the issue is not created and an error is generated. If instead from the same field I select a single value the issue is created successfully.
Thank you in advance for the help you give us

[Andy Heinzer · Accepted solution]

Hi Francesco,

I suspect that this problem could be caused by the plugin itself.  I understand there is an indexing problem here in regards to how Jira is trying to index this data.  It looks like the version of that plugin is listed as compatible with that version of Jira.

I would be interested to see if you can temporarily disable this particular plugin in Jira and then do a reindex to see if Jira can complete this.  Granted this would prevent the expected functionality of that plugin, but it would help to clarify if Jira is at fault or the plugin is.

It might help to create a support quests with Cprime, the vendor of this plugin, at https://jira.cprime.io/servicedesk/customer/portal/2 as they would be better suited to help if we determine that it's that specific plugin having problems indexing.

But I would be interested to see the results of a test like this.

Regards,

Andy

[Francesco Mazza]

Hi Andy
you suspect well because the problem is caused to a cPrime app. I have already been in contact for some days with the support of cPrime. The problem has been solved 80% just misses something. Let's say I was the guinea pig for their app on jira 8.2.2. :-) Anyway congratulations for your intuition. You hit the target. Thank you for your support.

Regards
Francesco