In Jira 8.4.0, creating issues with setSkipScreenCheck(true) is throwing Exception

Diamantino Campos

Hi team,

 

I've noticed that in Jira 8.4.0, when creating issues without verifying if a Custom Field is present in a Screen:

 

issueInputParameters.setSkipScreenCheck(true);

IssueService.CreateValidationResult result = issueService.validateCreate(user, issueInputParameters);

 

Jira is throwing an error due to ArchivedDateSystemField:

Not implementedjava.lang.UnsupportedOperationException: Not implemented 
at com.atlassian.jira.issue.fields.ArchivedDateSystemField.getRelevantParams(ArchivedDateSystemField.java:54) 
at com.atlassian.jira.issue.fields.AbstractOrderableField.populateFromParams(AbstractOrderableField.java:185) 
at com.atlassian.jira.web.action.issue.IssueCreationHelperBeanImpl.validateCreateIssueFields(IssueCreationHelperBeanImpl.java:80) 
at com.atlassian.jira.web.action.issue.IssueCreationHelperBeanImpl.validateCreateIssueFields(IssueCreationHelperBeanImpl.java:57) 
at com.atlassian.jira.bc.issue.DefaultIssueService.validateAndCreateIssueFromFields(DefaultIssueService.java:782) 
at com.atlassian.jira.bc.issue.DefaultIssueService.validateCreate(DefaultIssueService.java:742) 
at com.atlassian.jira.bc.issue.DefaultIssueService.validateCreate(DefaultIssueService.java:202) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:498) 
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) 
at com.sun.proxy.$Proxy76.validateCreate(Unknown Source) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:498) 
at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:131) 
at com.sun.proxy.$Proxy76.validateCreate(Unknown Source) 

 

A workaround for this problem is to create the issue first, with the default:

issueInputParameters.setSkipScreenCheck(false);

 and after updating the newly created issue with:

issueInputParameters.setSkipScreenCheck(true);

 

This problem only happens in Jira 8.4.0. I've tested and it works on 8.3.0, 8.4.1 and 8.5.0 eap 2.

 

Is anyone having the same issue?

 

 

Thanks,

 

Diamantino Campos

Ulrich Hobelmann [catworkx]

Apparently this will be fixed in the next release: https://jira.atlassian.com/browse/JRASERVER-69968