Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.3-OD-15
Description
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Steps to reproduce:
- Highlight a text in a Confluence page and click on the popup to create JIRA issue.
- Make sure the "Link to epic" is available and tick it.
- You will be faced with this error:
In the logs, I observed the following stack :
2013-12-11 16:14:42.974261500 com.atlassian.sal.api.net.ResponseStatusException: Unexpected response received. Status code: 400 2013-12-11 16:14:42.974271500 at com.atlassian.applinks.core.auth.ApplicationLinksStringReturningResponseHandler.handle(ApplicationLinksStringReturningResponseHandler.java:19) 2013-12-11 16:14:42.974273500 at com.atlassian.applinks.core.auth.ApplicationLinksStringReturningResponseHandler.handle(ApplicationLinksStringReturningResponseHandler.java:13) 2013-12-11 16:14:42.974274500 at com.atlassian.applinks.core.auth.trusted.TrustedApplinksReturningResponseHandler.handleNormally(TrustedApplinksReturningResponseHandler.java:40) 2013-12-11 16:14:42.974277500 at com.atlassian.applinks.core.auth.trusted.TrustedApplinksReturningResponseHandler.handle(TrustedApplinksReturningResponseHandler.java:28) 2013-12-11 16:14:42.974282500 at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:166) 2013-12-11 16:14:42.974282500 at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:351) 2013-12-11 16:14:42.974283500 at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161) 2013-12-11 16:14:42.974285500 at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.executeAndReturn(ApplicationLinkRequestAdaptor.java:78) 2013-12-11 16:14:42.974286500 at com.atlassian.applinks.core.auth.trusted.TrustedRequest.executeAndReturn(TrustedRequest.java:51) 2013-12-11 16:14:42.974287500 at com.atlassian.applinks.core.auth.AbstractApplicationLinkRequest.execute(AbstractApplicationLinkRequest.java:159) 2013-12-11 16:14:42.974289500 at com.atlassian.confluence.extra.jira.DefaultJiraIssuesManager.createAndUpdateResultForJiraIssue(DefaultJiraIssuesManager.java:474) 2013-12-11 16:14:42.974290500 at com.atlassian.confluence.extra.jira.DefaultJiraIssuesManager.createIssuesInSingle(DefaultJiraIssuesManager.java:313) 2013-12-11 16:14:42.974291500 at com.atlassian.confluence.extra.jira.DefaultJiraIssuesManager.createIssues(DefaultJiraIssuesManager.java:297) 2013-12-11 16:14:42.974294500 at com.atlassian.confluence.plugins.jira.CreateJiraIssueResource.createJiraIssues(CreateJiraIssueResource.java:70) 2013-12-11 16:14:42.974295500 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2013-12-11 16:14:42.974295500 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 2013-12-11 16:14:42.974296500 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2013-12-11 16:14:42.974298500 at java.lang.reflect.Method.invoke(Method.java:597)
Reasons: This is a known limitation where issues cannot be created with Epic links if the "Epic Links" field is not enabled as a field in a default screen in JIRA. Created with Epic links if the "Epic Links" field is not enabled as a default field in JIRA.
Workaround:
1. Not select an epic to link the issues to.
2. Add epic link as a field in default screen via secure/admin/ConfigureFieldScreen.jspa?id=1 with admin privileges.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-