-
Bug
-
Resolution: Fixed
-
Medium
-
19
-
Severity 3 - Minor
-
2
-
NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.
Summary
After upgrading to JIRA 7.1.2 Creating issue from Confluence not working when linked to epic
Steps to Reproduce
In Confluence select text and use the create issue in JIRA icon
Ensure that the checkbox 'link to epic' is checked
Expected Results
That the issue is created in JIRA
Actual Results
Create issue icon keeps spinning and the issue is not created in JIRA.
The below exception is thrown in the xxxxxxx.log file:
2016-03-28 16:48:59,642 http-nio-8080-exec-14 ERROR schristopher 1008x1723x1 5lpyr4 127.0.0.1 /rest/api/2/issue/bulk [c.a.j.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException 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.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:192) ... 4 filtered at com.atlassian.jira.rest.exception.ExceptionInterceptor.intercept(ExceptionInterceptor.java:55) ... 1 filtered at com.atlassian.jira.rest.v2.issue.scope.RequestScopeInterceptor.intercept(RequestScopeInterceptor.java:39) ... 15 filtered at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:154) ... 1 filtered at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:68) ... 91 filtered at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:70) ... 15 filtered at com.atlassian.plugins.rest.module.servlet.RestSeraphFilter.doFilter(RestSeraphFilter.java:37) ... 22 filtered at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.lambda$invokeFilterChain$0(CustomerContextSettingFilter.java:169) at com.atlassian.servicedesk.internal.util.scala.ScalaJavaInterOp$1.apply(ScalaJavaInterOp.java:25) at com.atlassian.servicedesk.internal.utils.context.CustomerContextUtil$.outOfCustomerContext(CustomerContextUtil.scala:48) at com.atlassian.servicedesk.internal.utils.context.CustomerContextUtil.outOfCustomerContext(CustomerContextUtil.scala) at com.atlassian.servicedesk.internal.utils.context.CustomerContextServiceImpl.outOfCustomerContext(CustomerContextServiceImpl.java:24) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.outOfCustomerContext(CustomerContextSettingFilter.java:164) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilterImpl(CustomerContextSettingFilter.java:120) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilter(CustomerContextSettingFilter.java:112) ... 55 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at com.atlassian.greenhopper.service.issuelink.EpicServiceImpl.addIssuesToEpic(EpicServiceImpl.java:90) at com.atlassian.greenhopper.customfield.epiclink.EpicLinkRestFieldOperationsHandler.update(EpicLinkRestFieldOperationsHandler.java:104) at com.atlassian.greenhopper.customfield.epiclink.EpicLinkRestFieldOperationsHandler.handleOperation(EpicLinkRestFieldOperationsHandler.java:76) at com.atlassian.greenhopper.customfield.epiclink.EpicLinkRestFieldOperationsHandler.updateIssueInputParameters(EpicLinkRestFieldOperationsHandler.java:64) at com.atlassian.jira.rest.v2.issue.IssueInputParametersAssembler$IssueInputParametersBuilder.finalizeIssueInputParams(IssueInputParametersAssembler.java:428) at com.atlassian.jira.rest.v2.issue.IssueInputParametersAssembler.makeCreateAssembler(IssueInputParametersAssembler.java:131) at com.atlassian.jira.rest.v2.issue.IssueInputParametersAssembler.makeCreateAssemblers(IssueInputParametersAssembler.java:138) at com.atlassian.jira.rest.v2.issue.CreateIssueResource.createIssues(CreateIssueResource.java:77) at com.atlassian.jira.rest.v2.issue.IssueResource.createIssues(IssueResource.java:624) ... 227 more
Notes
This was previously reported as a Confluence bug here: https://jira.atlassian.com/browse/CONF-41160
Further testing though suggests that this is in fact a JIRA bug. Customer on ticket GHS-37438 experienced this issue after upgrading from JIRA 7.0 to 7.1.2 while Confluence was on 5.8.13. I tested this myself by installing Confluence 5.7.6 and testing and was able to replicate the problem while connected to JIRA 7.1.2
Tested as well with Confluence 5.7.6 and JIRA 7.0 and was not able to replicate.
Workaround
No observed workaround at this time.
- is caused by
-
JSWCLOUD-10333 Updating epic link field through REST causes 500 Internal Error
- Closed
- is related to
-
JSWCLOUD-13407 Get an internal server error when trying to create an issue with Epic Link via REST API
- Closed
-
JSWSERVER-13429 Create issue from Confluence not working when linked to epic
- Closed