This would still be really useful in 2022

Hi all,

Thanks for your interest in this issue.

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

This suggestion will be reviewed in about 12 month's time, at which point we’ll consider whether we need to alter its status.

Best,
Confluence Product Management

I'm surprised you cannot disable the global templates from showing up in a space. It's nice that one can create global templates, but when there are lots of spaces, global templates can become less and less "global".  One can already disable blueprints, how obvious is it to disable global templates?

Agreed. In addition, some type of versioning as well as a better interface for the templates than just a list and edit? Perhaps folders/containers for them? I have near 100 templates and sometimes it is hard just to click the right edit button!

As a Space Admin, it would be useful to also be able to hide (deactivate) and/or promote global templates in a given space. We have about 12 global templates which are only relevant to about 50% of spaces and otherwise completely irrelevant.

I have this problem as well. I am using the Scaffolding plugin from Service Rocket and the Live Templates that are the source should not be selectable. At this point I have had to cryptically name thema nd put DO NOT USE as a description. Pretty ugly solution.

When running Confluence for a lot of years you probably have created a lot of templates. Some of them might be live templates using the Scaffolding Plugin. A huge amount of historical pages are based on them. If you decide to remove such a template, those historical pages are not displayed anymore. They have "lost" their contents due to the Template is not accessible exception.

If you do not remove those old templates, people tend to create new pages from them instead of using shiny new blueprints or different templates.

This blocks both process and creativity and leads to frustrated people in a corporate environment.

Please, make it possible to hide certain templates from the list of available templates.

My use-case is quite simple. I want to clean up among all the global templates but I don't want to delete them because I'm not quite sure which ones I want to keep yet.

Blueprints can be disabled, but why not templates?

We use SQL code in some Global Templates (live templates) that are used by other pages to display data. These are not useful to end users to create on their own and it would be nice to hide them.

Out company is large and very heterogeneous. On the one hand the users ask for structures like templates on the other hand the demands are very specialized. When creating global templates I more or less give recommendations how to structure a page. But each department likes to have some addons to the global structures which are quite individual. Their way is to duplicate that global template and to create one with their own specifics. Keeping the global templates helps new born spaces to adhere given structures for cross-space benefit but as soon as they discover self-created templates they like to "replace" the global one by deactivating it. As soon as they mature in using wiki they have to handle multiple templates where half of them won't be used in their space but still shown. From their perspective this is not focused to the essential as the rest of the wiki seems to realize though.