See CONF-20426.

If JIRA and Confluence are installed on the same machine and on the same context path, then it's impossible to add JIRA gadgets to the Confluence RTE. You can still paste the gadget XML into the wiki markup editor.

What does this mean?

a) Different servers: http://myserver:8080 + http://yourserver:8080
b) Same server, different context path: http://myserver:8080/jira + http://myserver:8081/confluence
c) Same server, same context path: http://myserver:8080 + http://myserver:8081.
Scenario (c) is the problem, (a) and (b) appear to be fine.

This configuration is normal in two cases:

1. Any customer following Here Be Dragons (550+ customers to date)
2. Anyone using the Inception Installers for JIRA and Confluence on the same box. (most BTF customers from mid-to-late 2011).

What's the customer effect?

JIRA gadgets become useless in Confluence pages without an opaque workaround which will become impossible on the release of Confluence 4.0. For example, it's impossible for a customer to build a release dashboard in Confluence. We've had to yank that functionality from the Dragon's guide today as "please paste this opaque blob of gadget XML into a page" is a shit user experience.

Solution?

We need a solution that allows customers to deploy Atlassian applications on the same server and still be able to use gadgets.