-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
3.5
-
None
In versions of Confluence prior to Confluence 3.5, a version of Atlassian Application Links was included that featured the ability to automatically turn textual references to entities in other applications into hyperlinks (for example, you could type "PROJECT-123" into a Confluence page and, if you had an entity link configured to a matching JIRA project, the issue key would be transformed into a hyperlink to "http://my-jira/browse/PROJECT-123" when the page was viewed).
This feature was removed from Atlassian Application Links 3.0, which is the version of Application Links that was shipped with Confluence 3.5.
Any customer that upgrades to Confluence 3.5 from an earlier version will find that any application links such as this that were visible on their Confluence pages have now reverted back to plain, unlinked text.
A new, separate plugin was written for JIRA to restore this functionality (https://plugins.atlassian.com/plugin/details/559566), but it doesn't work in Confluence.
- relates to
-
CONFSERVER-36053 Application Link issue key not rendering after migration from Cloud instance
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
[CONFSERVER-23693] Application Link Link Rendering does not work in Confluence 3.5 or higher
Hi Gaurav,
In the current versions of Confluence you can use the JIRA issues macro and the Insert JIRA Issue dialog to embed JIRA content in Confluence pages.
Additionally, if you paste a JIRA issue URL into the Confluence editor, it will automatically be converted into a jira macro.
Regards,
Joe.
Gaurav Mishra
added a comment - what does the current version do then? nothing? After some discussion, we have decided that we will not be able to offer a supported migration path for this situation.
AppLinks 2.0 was only included by Atlassian in JIRA Studio installations. We did not anticipate that it would be used seriously by customers running 'behind-the-firewall' instances of Confluence.
The functionality that this feature used to provide has now been replaced by the {jira} macro.
This is a critical issue for us. I would imagine it would be the same for other customers upgrading that have JIRA linked this way. These links are used all over in our installation - pages, user macros, queries, scripts. Changing to some other scheme is a major headache and will significantly delay upgrading.
- What is the time frame for looking at this?
- Was there some specific reason for NOT carrying this forward or just a matter of not yet getting it working again in Confluence?
- Is the intention to provide a plugin that adds this back in similar to the JIRA one (at least until the bundled support gets it added)?
We just hit this now in moving from On Demand to local, so it's not an issue that's gone away. I just want to point out that you made this WAY harder to use, apparently without apology, and my users are pretty upset. "Use this much harder/slower/longer to type thing, it's OK!" is really uncool.