Hi @guiliano

Re: "We are currently shifting the efforts from templates to additional customization options for Confluence Cloud."

I totally understand needing to redirect efforts, and that other improvements may enable this user story. What I would like to know is how Atlassian will enable this workflow, even if not by fixing this specific issue. Please let us know. 

@lissa Meade

That didn't seem to work for me. Regardless of where I instantiate the template, create from template always puts the new template in the space specified in global template. 

There has been a fix, at least in my Confluence Cloud instance. You just have to set the space to whatever in order to add it to the template, then when you actually create a page from the template it will update the space key to the one you are currently in. 

I need to be able to create a hierarchy of pages from a template... the Create from template macro is the only way to do that, but you still can't use it in a Global Template because the Space Key is mandatory. 11 years later and it's still not possible. 

Hello everyone,

We are currently shifting the efforts from templates to additional customization options for Confluence Cloud.

While we will not be closing this suggestion, this means that we will be pausing the implementation for new features related to templates, but will keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy.

Thank you for your understanding.

I'd say that there is mistake in Steven Behnke's comment above.
He said that

Space Template do NOT have this problem

but really Space Template has this problem too.
You can't use Create From Template macro in both, Global and Space Templates.

And yes, copy/paste does the job.
And strange why Atlassian coudn't fix this bug for years.

Well done Steven, wish I'd spotted your comment before I was just about to post a similar work around

I propose this be addressed as a bug or at least looked into more quickly as this is irregular and feels like unexpected behavior.

Bug

It appears that the issue here is that when you are in a Global Template edit action (I am SPECIFIC here because Space Template Edit actions do NOT have this problem), the macro parameters do not load correctly. Please inspect my screenshot.

Workaround

• Add the macro on an actual page draft
• Modify the macro parameters as desired
• Use your system copy (CTRL+C/CMD+C) to copy your macro from your page draft
• Use your system paste (CTRL+V/CMD+V) to paste your macro into your global template

The macro (storage format) will be pasted into the editor with it's parameters intact.
Working example

<ac:structured-macro ac:name="create-from-template">
<ac:parameter ac:name="createResult">edit</ac:parameter>
<ac:parameter ac:name="blueprintModuleCompleteKey">com.atlassian.confluence.plugins.confluence-software-blueprints:jirareports-blueprint</ac:parameter>
<ac:parameter ac:name="contentBlueprintId">51826ad4-03d5-47cd-b161-712c778c8e09</ac:parameter>
<ac:parameter ac:name="buttonLabel">Create from template</ac:parameter>
<ac:parameter ac:name="templateName">51826ad4-03d5-47cd-b161-712c778c8e09</ac:parameter>
</ac:structured-macro>

Bugged example

<ac:structured-macro ac:name="create-from-template">
<ac:parameter ac:name="buttonLabel">Create from template</ac:parameter></ac:structured-macro>

I confirm the above comment (Fabrizio Galletti 10/Oct/14)
You can prepare the button on a standard page and copy-paste it to Global Template.
Of course you won't be able to change the parameters of the button on the Global Template page, but it will work as expected.

I've used it, with copy and paste from a standard page if i remember well