Confluence backup for migration affects Jira Issue macro links
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Problem
Creating a backup of your Confluence instance, to import into an installed Confluence instance, affects Jira Issue macro with the warning:
"Unable to render Jira issues macro, execution error."
Cause
The Jira Issues macro was requesting the old server parameters because of the bug CONFSERVER-31026 - Confluence Space Export/Import Affects JIRA Issue Macro Links. For example:
<li><ac:structured-macro ac:name="jira"><ac:parameter ac:name="server">StreamTheWorld JIRA</ac:parameter><ac:parameter ac:name="key">MYSQL-489</ac:parameter> |
|---|
Workaround
- Take a backup of your database.
Run through Alternative Methods of Deleting Application Links in Confluence to delete the current application links in your local installed Confluence instance. Basically you just need to run:
DELETE FROM BANDANA WHERE BANDANAKEY LIKE '%applink%';- Then restart Confluence.
- Create a new application link between Atlassian OnDemand and your local instance. Make sure you select that you're using a different user base, and the servers trust one another fully.
- Edit a page that already has a JIra Issue Macro that isn't working, insert a new Jira Issue Macro immediately after the broken one. This should work with your new application link.
- On the page you just edited click: tools->view storage format.
Search for
'<ac:parameter ac:name="serverId">'. Immediately after this tag you'll see the ID of the broken application link, note this down.Search for
'<ac:parameter ac:name="serverId">'again. You should find the working server id, note this down as well.Run the following SQL:
update bodycontent set body = replace(body, 'ID from step 7', 'ID from step 8');- Go to your Cache Statistics screen in Confluence Administration and click 'Flush All'.