As a user I would like to include specific content from a Confluence page in a Jira issue so that I only have one source for requirements descriptions

Confluence content should be embeddable on Jira issues but only editable in Confluence. This makes the Confluence page the source of truth for the content, but users don't need to leave Jira in order to view it.

For example, I have a definition of Ready and Definition of done all in the same confluence Page.
It would be great if I could display the text relevant for the Definition of done in the description of the Jira ticket.

The Text should at least be fetched when I create the Jira ticket:

Thought would have to go into whether the text should continuously update or not, since that could mean that specifications suddenly change without anyone knowing, and old tickets would suddenly show texts that weren't true or relevant yet when the ticket was first created.

Ideally you could do both, a one time fetch or a fetch that continuously updates each time the Jira ticket is opened.

Original Description

We have both Jira and Confluence in house today.

Our requirements elaboration process is more or less like this:

Whiteboard > Balsamiq > Axure > Jira epic > Jira user stories > Development > "Move content to Confluence for both description of business rules as well as the user manual".

Some time after release the improvements are registered. Minor adjustments to make it just a little bit more user friendly, changes to the business rules, etc. This is normally done in Jira. However, we see very often that we forget to update the business rules section in Confluence.

So we would like to change the process a little - to get down the requirements in Confluence first before we start creating Jira issues. And when we start creating Jira issues, we only reference certain placeholders or similar on a specific Confluence page. This will ensure that the content in Jira is updated continuously as there is only one true source of descriptions.

This "one source" idea is used by eDevTech with their product InteGREAT that manages requirements gathering and management together with TFS.