Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now.

Thanks again for your idea.

Bill Arconati,
Confluence Group Product Manager

The tagging process would certainly be a useful addition, but the real power would come if you could aggregate information about these tagged versions across multiple pages to create reports similar to what the metadata-plugin does, but for arbitrary versions of pages, not just the latest.

We ended up writing a custom plugin that provides this functionality. A Revision table macro that lists the previously tagged versions that can be placed on the page, and shows the metadata that was entered when the page was tagged. And an aggregation macro that can show the latest tagged version of many documents in a large table, along with a selection of the metadata. You can then lock the version that the aggregation macro refers to on a page by page basis and use it as a historical reference since it provides a link to the old version of the page.

We use this for running test cases and ever completed execution gets a new tag. The metadata that goes with the tag indicates the results of the execution. And a results table for a whole suite of tests can be compiled automatically. This saves considerable time editing a large results table, and means that no-one needs to edit the large table so multiple testers are not waiting for each other to finish editing the table. We can then lock the versions after a release so we have a snapshot of the test results when a specific version of the software was released. We create a separate page the results table for each release by copying the previous one.

David,
Would tagging a page with a 'tag name' like when using source control cover this functionality? Or are you doing the 'copy process' to achieve a sort-of 'page template'?
Cheers
Matt