We like to put the System Requirement Specification for our project in Confluence and from this create issue in Jira based on the requirements in Confluence. We also want to create mutual links between Jira issues and confluence requirements that needs to be unambiguous. As I can see there is really good and simple way guarantee that the confluence page doesn't change after the link have been created resulting in that the requirement, which gave rise to the issue and that the issue is linked to, no longer match the issue. For legal reason we need to be able to track all software releases back to the requirement applicable at the time for the software release.
Keeping the JIRA user stories in sync with the requirements in Confluence is a challenge we also encountered. For now we are using Confluence to draft the list of requirements along with other technical design specifications, but then we further groom the tickets in JIRA. We also noticed that when you automatically create tickets from Confluence, the result is truncated which is why we are leaving the stories defined in Confluence requirements pages as merely the starting point. For us, it is essential that the JIRA ticket description always remains up to date, accurate and complete. We will modify it during grooming or if discussion in the comments reveals a need for clarification.
This doesn't necessarily answer your question, but it would be nice for Atlassian help and provide a solution or guidance about this. Drafting requirements in Confluence is very effective for planning, but essentially you will have duplicate data then when creating user stories unless the requirements page could somehow sync with the newly created tickets.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG