-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
5.5.3
-
Standalone.
-
25
-
Severity 2 - Major
-
26
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Issue Summary
When creating a mirror image for testing purposes of our Jira instance, we then need to delete the application link to the Production instance of Confluence.
This then breaks the application link between our Production Jira and Production Confluences as well. The only solution that has worked is to delete then re-add the application links on both sides (same URL as was there in the first place).
Expected Results
Since the macro is saving the issue number, and the Jira link is the same (just re-adding it), I shouldn't have to go through every Confluence page containing a Jira macro just to re-find information that's already populated in it. Ideal behavior is for the macro to take the existing search query it contains and search in the new application link for it, THEN issue an error if it can't find it.
Actual Results
Jira macros in Confluence display "Error rendering macro 'jira' : Unable to locate JIRA server for this macro. It may be due to Application Link configuration".
Workaround
To fix individual instances:
1. Edit page
2. Edit macro
3. The macro still contains the issue number. Click the magnifying glass, re-find the correct issue.
4. Save page.
To fix in bulk:
Please see 'Unable to Locate JIRA Server For This Macro' displayed after changing JIRA Application Link name.
- is cloned from
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-34998] Updating Application Link cause rendering problem: "Error rendering macro 'jira' : Unable to locate JIRA server for this macro. It may be due to Application Link configuration"
Same issue in Confluence 7.4 .7, noticed by a team that migrated to our Confluence a while back but only just now migrated to our Jira. If the same issue is linked again below the broken link, it works. In the database, the two macros appear identical except macroid.
We're experiencing the same issue.
On seperate servers for Crowd, Jira, Bitbucket and Confluence we've restored production data (both database and application home directory). We changed the application configuration (to have it point to the testing servers/URL's), deleted and then re-created the Application Links (which also didn't go smoothly due to remaining references in the Confluence database). Everything seems to work fine.
However...
On one page in our testing environment I've found that both Jira Issue/Filter macros in the page were broken. Other pages don't suffer from this problem.
Editing this specific page and fixing the broken macros (by simply clicking the spyglass icon in the macro's Edit dialog) solved the issue.
When comparing both versions of this page I noticed that the before and after version of at least one macro had different ServerID's. Please check on your instances if my observations match yours.
Same here after update from Confluence 5.10. to 6.0.4... 
The First JIRA issue display the rendering macro... The ID etc is the same. Strange thing 
I have the same issue with upgrade JIRA to 7.1.9 and Confluence 5.10.6. Recreated the application links between Confluence and Jira. All works well, except the issue macro to JIRA.
The 'workaround' mentioned above does not work in my case. Only if I copy the macro completely, the copied macro works correctly, but the original macro, alhough it looks exactly the same in source editor, does not work with following error:
Error rendering macro 'jira' : Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
Server id's are exactly the same according to Source Editor. First one however, gives above error.
{{
<ac:structured-macro ac:macro-id="69fe05b0-fa0b-476a-9f22-235711c81054" ac:name="jira" ac:schema-version="1">
<ac:parameter ac:name="server">MY Jira</ac:parameter>
<ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution</ac:parameter>
<ac:parameter ac:name="serverId">xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</ac:parameter>
<ac:parameter ac:name="key">SYCM-51</ac:parameter>
</ac:structured-macro>
</p>
<p>
<ac:structured-macro ac:macro-id="d24e0e75-fc87-458f-8105-ba59b09e17fc" ac:name="jira" ac:schema-version="1">
<ac:parameter ac:name="server">MY Jira</ac:parameter>
<ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution</ac:parameter>
<ac:parameter ac:name="serverId">xxxxxxxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx</ac:parameter>
<ac:parameter ac:name="key">SYCM-51</ac:parameter>}}
I am also having the same issue. We recently moved from jira cloud to jira server and got this issue.
It would be great if you could give us a workaround for all confluence pages.
Thanks.
Adding to say:
When keeping a page open that has this error, our logs go nuts with the following error:
2014-09-24 14:28:31,376 WARN [http-bio-8090-exec-11128] [xhtml.view.macro.ViewMacroMarshaller] marshalInternal Exception executing macro: jira, with message: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
– url: /pages/viewpage.action | page: 4785155 | userName: ((DELETED)) | action: viewpage
Request an update pls