Please build this feature! It would help me so much for today and tomorrow's upcoming work this year. 

We use JIRA/Confluence Cloud and we have a workflow that keeps documentation pages for specific long term information.  When we create a Jira issue that references the page/table we would like for that long term information to be shown in the Jira issue for easy referencing.  This would be a huge help to our workflow, also updating the table/page in Confluence from the Jira issue would be awesome as well! 

Please build this feature! It would help me so much for today and tomorrow's upcoming work this year. 

community of practices often have desired ways of working documented in confluence. When a certain Jira story involves one or more of this recommendations, I would like to add said page(s) onto the story description itself. I don't think a custom field will work in this instance as I most likely want to add different pages depending on requirement. it would be better if its tagged in description and maybe when story/task/epic is closed, the version of that embedded page is saved.  

This would be super useful:
1. Create Custom Field in Confluence.
2. Create Custom Field in JIRA.
3. The Custom Field in JIRA can be configured to show the value that is from the Custom Field in Confluence.

should be done!

in cloud as well

Also super interested--and frankly a little shocked it's not supported.  It's seemingly a simple integration once you have both server-based products linked so why no ability to surface Confluence content in JIRA?  I would absolutely LOVE to be able to have power users author guidance that's shown on an issue (e.g., in sidebar), ideally with the ability to target what's shown on different statuses.  Can someone at Atlassian comment as to why this years-old issue isn't getting any traction?

I am also interested in this feature as it would help standardize workflow process referencing confluence standard documentation that can be maintained in one central location.

I am also interested in this feature.  The teams I work with would like to manage a Definition of Done and Definition of Ready at the team's Confluence page and then when creating and updating an issue of a certain type (ie: epic or story or feature), show the team's definition of ready and definition of done confluence excerpt in the Jira Issue being created or updated.  Would like to also associate the excerpt to the Jira team.  This way if you move the issue to another Jira project, the correct definition of ready and done shows in the Jira ticket. Looking to maintain the text in Confluence and display in JIRA.

@christian.mueller7, we create a Software Requirements page in Confluence, and create Epics from there. On each of the requirements sub-pages, we have a table with more detailed sub-requirements. We then text-select the first entry in the table, and use the popup to create a Jira issues from there. Ticking the 'batch create from table' option, removes some of the triviality of the task.

This creates Jira issues with a name from the requirements and bi-directional links from the issue to the full requirement and its context. The method is far from optimal, but better than nothing and a lot better than copy'n'pasting of requirements.

i am also interested in this feature - as the first request was 3! years ago - is this still in discussion and why was this not included yet ? i mean , is everyone copy/pasting requirements ?

Since this issue has been idle for a bit, lets breath some life into it.

Like prior comments, Confluence is brilliant for the construction of content - collaboration is now common place and we have review and approve workflows built to establish baseline ready.

Revisions to this content after the JIRA issue is created is often neglected. Project teams work entirely from JIRA, only stakeholders and the product owner / BA are active in Confluence so a synchronization between the two – always showing the current Confluence content is going to be a huge win. I've tried the scripting work around, publishing Confluence as plain text to an external URL, changing behavior to work from Confluence first and embed JIRA within Confluence. All are falling short.

Anyone found a more robust / reliable solution yet?

I like this idea a lot, but I'm a little worried about how history tracking (and notifications) would work. Would edits to the embedded Confluence page show up in the JIRA ticket's history log? Would it respect the different permissions between the two tools? There's so much data to keep tabs on, and it sounds like Atlassian wouldn't build this if it was just a type of 'excerpt' support. Seeing how requests have been implemented in the past, they would work something like this into larger plans for deeper JIRA+Confluence integrations in general. They're not going to build it one way temporarily just to throw all that code away for the "for real" implementation two releases later.

This really feels like a good candidate for a third-party add-on. Businesses that want this would happily spend the extra cash for it.

Our scenario is similar, but not mentioned yet is that our setup involves users who may only have access or Jira or Confluence, not both. For example, we cannot give clients access to Confluence (due to security issues well documented CONF-1882). However, if we could include snippets in Jira of Confluence pages, we could share pieces of a specification/documentation/etc. with our clients.

Beyond that, not having to copy/paste - not to mention edit/update - documentation between Jira and Confluence is needed for many other reasons discussed in the link Amy references above. Any comments on why you should not do this or do that though should be ignored though as the Atlassian apps should be flexible enough to allow users to use the system however they so choose.

I think Confluence => JIRA is the way to go.
I would like to use Confluence to document and collaborate on requirements. From there, I would want to create JIRA issues (exists already). But, I would also like to have select stories/features/scenarios automatically inserted into the JIRA issue, so I don't have to copy/paste (please retain formatting!) and so the user (developer) isn't bothered to click a link they may or may not see. It's hard enough to get someone to read the requirements.
Also, I think any ability to continuously update JIRA should be optional as JIRA issues that are completed would not have the latest requirements, imo - a new JIRA issue to implement the change should be created and have the latest requirements inserted into the JIRA description or other custom field.
FYI, this is the one missing feature that is preventing my manager from making a purchase and installing Confluence.

Multiple people have had this same request. In fact, the creator of this story has also participated in this discussion.
https://answers.atlassian.com/questions/191893/how-to-embed-confluence-content-in-jira-issue-or-vice-versa

Hi, why not doing it the other way around by creating the requirement in JIRA and inserting that issue in Confluence while displaying the description. This way, you have your content stored at one place (JIRA) and displayed in Confluence (knowing it will always be up-to-date). Check the AJIIM macro (http://bit.ly/1kwt9uJ) that let you insert JIRA issues in Confluence page including the description in a way that is a little bit more suited for specifications than the JIRA Insert macro.