As the first commenter on this issue back in 2006, and since it is now officially an adult, cheers! 🍻

7914a5fba7f8 - I'm finding ISO compliance to be painful in Confluence. Aside from all the changes they make and roll out without concern for controlled environments (yet their slogans are all about empowering "every team" - clearly not teams that have compliance requirements).

On this ticket - firstly, happy 18th birthday ticket! Secondly, why is this not a thing? Templates of ALL things should be controlled with change histories.

I can't say I am surprised to find yet another fairly basic request ignored. Initially, the (lack of) response here seems to align with Atlassian's apparent philosophy to reject requests for features that can be addressed via a workaround. I take issue with this philosophy but, for the sake of argument let's examine this request under the assumption that we philosophically agree.

What solutions are being provided by templates that could not already have been addressed by a workaround? Essentially why should we use templates over normal pages? Currently, normal pages offer features like a page history, among others, while having few drawbacks compared to templates. There seems to be insufficient incentive for the use of templates. If templates do not have a sufficiently distinct use case, seemingly required by Atlassian's philosophy, there are two options:

1. Improve the functionality of templates. Address the drawbacks compared to the "workarounds". There should be no downside when choosing to use templates. Then incentivize the use of templates with functionality improvements to distinguish them from normal pages. This would be preferable and I wish most requests would be approached this way, even if they do not all work out.
2. Alternatively, remove templates and any other unnecessary or redundant features or functionalities. Do not waste any resources where there is no unique value. Redistribute the wasted resources toward the maintenance, improvement, and implementation of truly unique features. While this is not preferable, it is at least consistent and opens the door for more noticeable improvements elsewhere. 

Soon we are going to have a new generation adding to this interest

Concur.  Valuable enhancement.

As mentioned above template actually are versioned it is just not exposed in the interface. You can see the versions in the database

select *
from PAGETEMPLATES
where TEMPLATENAME = 'Your template name'

For user macros I created an app that allows you to keep versions of the user macro. I also fix a bunch of other annoyances with User Macros. It's a free app.

Enhanced User Macro Editor

For ISO certified organizations and all organizations in regulated industries, this is absolutely essential. Templates require versioning, end of story. 

Definitely going to weigh heavily in our decisions regarding whether or not to keep our company subscription to confluence.

Hello!

We understand that it would be great to have Templates versions control features OOB, but if you are interested,

we released https://marketplace.atlassian.com/1220906 (paid) plugin.

It has simple options of templates versions control.

Thank you

This really is a must-have feature to use confluence in a regulated industry like medical devices - we are required to have certain "document controls". And this includes managing versions of page templates. 

Of course, this is not only required for these industries, this would also be a very useful feature!

I am a lowly space admin, no chance they are letting me near the SQL

I can see one addin that does something with import/export, Template Ops, but it looks out of date, only says it supports v5. Anyone know of a v7 supported alternative?