-
Bug
-
Resolution: Fixed
-
Medium
-
6.0.0-OD-2016.02.1, 6.0.0-OD-2016.02.1-0006, 6.6.4, 6.6.5
-
80
-
Severity 2 - Major
-
106
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Summary
The JIRA 'Change log' Report creator in Confluence no longer works.
When attempting to create a report the screen the 'loading' icon is displayed indefinitely and the report never loads.
This worked in 5.9.4, and broke in 6.0.0
Environment
- Confluence Version 6.0.0-OD-2016.02.1-0006
Steps to Reproduce
- In confluence click on the '...' next to the 'Create' button in the top menu bar
- Select 'JIRA Report' and click 'next'
- Select 'Change Log' and click 'next'
- Select a Project from the drop down menu, leave other fields as default and click 'create'
Expected Results
- The report is created and the page is loaded
Actual Results
- The loading icon will be displayed indefinitely and nothing will happen, the report is not created
- The below exception is thrown in the logs
ERROR [http-bio-1990-exec-16] [common.error.jersey.ThrowableExceptionMapper] toResponse Uncaught exception thrown by REST service: com.atlassian.confluence.extra.jira.JiraIssuesManager.retrieveXMLAsChannel(Ljava/lang/String;Ljava/util/List;Lcom/atlassian/applinks/api/ApplicationLink;ZZ)Lcom/atlassian/confluence/extra/jira/JiraIssuesManager$Channel; -- referer: https://<omitted> | url: /wiki/rest/create-dialog/1.0/content-blueprint/create-draft | traceId: 5427a38ed50bfa63 | userName: <omitted> 2016-01-12 11:55:16.303976500 java.lang.NoSuchMethodError: com.atlassian.confluence.extra.jira.JiraIssuesManager.retrieveXMLAsChannel(Ljava/lang/String;Ljava/util/List;Lcom/atlassian/applinks/api/ApplicationLink;ZZ)Lcom/atlassian/confluence/extra/jira/JiraIssuesManager$Channel;
- Error showing in the Chrome browser Console:
POST https://<site>.atlassian.net/wiki/rest/create-dialog/1.0/content-blueprint/create-draft 500 (Internal Server Error)
Workaround
"switch to advanced" prior to hitting "create" works for some users
Resolution
Upgrade to Confluence 6.6.10+, or Confluence 6.8+
Note that this issue is not fixed in Confluence 6.7.x
- has a regression in
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
PSR-145 Loading...
- Testing discovered
-
-
- Closed
-
![[JIRA]](/images/icons/generic_link_16.png "[JIRA]"){kind=icon}
[CONFSERVER-40451] Confluence 'Create JIRA Report - Change log' doesn't load
We are pleased to let you know that the fix for this issue has been backported to the upcoming enterprise release Confluence 6.6.10 which is due to be released soon.
Regards,
Niraj Bhawnani
Senior Development Team Lead, Confluence Server
Atlassian
Any reason why this is not going to be fixed in Enterprise Release 6.6.x?
SEE ISSUE LINK : REGRESSION
This bug is still being tracked but on a regression ticket!
We just had this issue today on:
- Confluence 6.6.2
- Jira 7.7.0
Please re-open this issue, it is clearly not fixed.
I.
Hello. I am running Confluence Server version 6.7.0 and am still getting the "we can't create that blueprint right now" error.
Switching to advanced does provide a workaround, but that then doesn't allow me to break apart the issues by issue type. That feature is a very helpful part of the release notes, enough so that it was called out in the tutorial.
Confluence will automatically break your release down into "Bug Fixes," "New Features," "Improvements" etc. based on the issue type in JIRA. This automation is really helpful and eliminates the need for lots of manual editing and formatting.
If you're running the Confluence 6.6 Enterprise release, a fix for this issue is now available in Confluence 6.6.10, which you can find in the Download Archives.