also for me should be very useful

+1 would like to have this feature

+1. We use components and mini projects with in larger projects and those each have their own set of requirements. Please reconsider this issue and implement.

+1

+1

If I'm not mistaken this one is related: https://jira.atlassian.com/browse/JRASERVER-64169

..and they're gathering interest there.

..and this one would at least provide a workaround if solved: https://jira.atlassian.com/browse/JRASERVER-39696

+1

We use components (and the subcomponent plugin) to manage 900+ objects, with each object having a specification (currently word doc)

We want to bring those specs into Confluence but need to be able to link them to their corresponding component

+1

It would make documentation way easier.

Most of the time, documentation is related to a functional block (usually a component in JIRA), not to a single issue.

Imagine you want to document in Confluence an interface with an external software, and this interface has 100+ related issues.

In order to access to this page from an issue, you have to create one Jira macro (in Confluence) for each issue (since JQL does not create a link in JIRA), which is just not possible.

+1 for this functionality

One example of the usefulness of this would be filling a gap in Atlassian's support for bi-directional traceability between application content types, which is a basic requirement of several standards and process frameworks that teams may need to be compliant with. While a Confluence space can link to a JIRA project (weakly) and bi-directional linking is pretty robust between any combination of issues and pages, that's about all we get. Considering components are often 1:1 representations of elements defined in documentation, it's a little bizarre that there's no way to create an actual link from them to the source.

What's frustrating is that it seems like improving JIRA-Confluence integration was being pursued at one time. Links between Epics and pages are detected and shown in JIRA Software's backlog planning view as part of the epic pane's design. However, the other pane (versions) lacks this, as versions lack the ability to be linked to Confluence pages at all, despite the fact that Confluence comes with page blueprints for releases right out of the box. While this can be addressed from the Confluence side with a JIRA issue macro, that macro is not a traceability solution.

Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. If you are able to describe your higher-level goals we may be able to provide better guidance. Thanks again.