CSV Export of all fields failing with network error
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
CSV export of all fields fail with "Network Error"
After a search, when selecting the Tools option to export all fields to a CSV file, the export fails with a "Network Error" message. Exporting just some fields works as expected.
環境
8.13.11
.
診断
Atlassian-jira.log shows that one of the Custom Fields is causing the CSV export to fail:
2021-10-06 09:31:55,113-0700 https-jsse-nio-8443-exec-36 ERROR xxxxxx 571x941872x5 1vagklv /sr/jira.issueviews:searchrequest-csv-all-fields/temp/SearchRequest.csv [c.o.s.c.j.f.editable.ldap.LdapPicker] Failed to retrieve view html from LDAP for field customfield_12400: null
2021-10-06 09:31:55,117-0700 https-jsse-nio-8443-exec-36 ERROR [o.a.c.c.C.[.[localhost].[/].[searchrequest-view]] Servlet.service() for servlet [searchrequest-view] in context with path [] threw exception [Servlet execution threw an exception] with root cause
java.lang.Exception: Field config should not be null
at sun.reflect.GeneratedConstructorAccessor2226.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:80)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:249)
at com.onresolve.scriptrunner.canned.jira.fields.editable.ScriptFieldConfigProvider.getConfigurationForFieldInternal(ScriptFieldConfigProvider.groovy:61)原因
The CSV export was failing when selecting all fields because one of the Custom Fields was corrupted.
On this specific sample, the custom field corruption was introduced after upgrading Jira to 8.13.11, using Adaptavist ScriptRunner for JIRA version 6.35.0.
回避策
All the Projects are affected by the issue. While the custom field is not fixed or removed, it is possible to mitigate the impact restricting which projects can access this custom field (these projects will remain being impacted), changing the configuration context:
- Jira Admin > Issues> Custom Field
- Click the engine icon at the custom field line and select "Configure"
- Edit Configuration
- Instead of selecting the 'Global context', select a single project not used by the export or only the projects using this field.