Hopefully I am not the only one struggling with this issue regarding baselines. What I'm trying to achieve is just a versioned document that links to a set of versioned JIRA issues. Doesn't sound to hard to achieve but how do you lock those issues from being edited so that a certain baseline always reflect a certain version of the issues it holds links to?
Detailed description of the problem.
On day one I create this Confluence page that contains requirement specifications using the "Product Requirements Blueprint"-approach described in the Atlassian documentation. This page holds a table pointing out several product requirement documents which in turn contains several links to JIRA issues where the requirements are described in detail.
Obviously on day one they are all in synch with what we want since this version of the document, version 1, contains the specified requirements as of right now. Then at some later point in time someone discover that one or more of the requirements need to be updated, which is rather common, and they would have to update the requirements issues in JIRA. This is where the problem is. If we change those requirements issues then they are not the same as the ones we added at day one which makes the baseline useless.
As far as I know Confluence has only got individual versioning of pages. Unfortunately that doesn't solve this problem since it points to other documents (through the "Page Properties Report-macro") which in turn contains links to the requirements in JIRA.
The real question is:
How can you achieve a proper baseline handling in JIRA/Confluence whereby the top page, containing the Page Properties Report macro, points at a specific version of the requirements documents which in turn hold specific versions of the requirements issues in JIRA?
Hope this problem description makes sense.
