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

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.