Please see and vote at: https://jira.atlassian.com/browse/CONFCLOUD-29581

I have reopened this issue....Please see: https://jira.atlassian.com/browse/CONFSERVER-94538 

I could not update description after cloning this issue though, so description is in the comments. 

Feel free to include OTHER PARAMETERS you would like in comments. Maybe with enough votes, they will listen to us!!!!

Why it is not considered?!

We want this feature as well.

Suggested parameter "fromPageId" is not working - https://community.atlassian.com/t5/Confluence-questions/Create-from-template-under-specific-page-in-another-space/qaq-p/943885

I find it slightly humorous this was created in 2014!  In 2018 it was marked as Not Considered.  Obviously the simple features like creating a page under another page are too hard for Atlassian 

is there any solution atm? or any workaround that works?

maybe with HTML? please let me know

Without the ability to specify the parent page under which to create a new page, this macro is annoying to use. +1 to please review the request.

I really need to create pages from a template in a different restricted visability space. This is in the case when users fill forms that have sensitive information and are collected in a restricted space not visible to all. 

We would like to use this feature too. Please review it.

Please review this potential really interesting feature. It would be nice to specify a parent page in the macro to keep a space clean. 

We tried to use the workaround here but it doesn't really work: https://community.atlassian.com/t5/Confluence-questions/Create-from-Template-and-Specify-Parent-Page/qaq-p/290661 

Any updates on adding feature to this macro? This really clutters our wiki space with pages in inappropriate locations

Be good to see this enabled in Confluence templates. Can it be reviewed again please?

It's now one year since this issue was tagged "not being considered". It is time for a review.

Completely agree with your other customers users above - this is a very obvious use case - this macro could be very powerful, but is almost useless without more options.

+1 for "Parent Page" attribute. Currently this macro litters my carefully curated space with rogue documents

It would be great to see the Macro support "Parent Page" selection for another Space.

I am impacted by this, but there are so many community questions asking about doing this as well,  The main issue is that a lot of companies lock down their Confluence administration, so that people cant implement custom macros.

I really don't understand why you didn't put Parent Page in the macro to begin with; sounds like the customer journey wasn't really thought about - being able to create in another Space is great, but if doesn't allow a parent page selection in that space, the space will become very messy and disorganised.

My specific Use Case: As a change manager, I initiate collection of feedback from users on multiple pages within a restricted space, but as feedback may come from anonymous users I require the feedback items to be created on a Space where I can open the permissions to anyone. All of this feedback I want to have placed under a parent page in this second space called "Feedback", so that it doesn't make the page tree full of items that make navigation difficult for other users of the space.

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 months time, at which point we’ll consider whether we need to alter its status.

would love to see this

+1, ah to hell, make it +2

This is ESSENTIAL. Especially for creating meeting notes and not having to reorder the space every time someone uses a "create from template" macro to make meeting notes. 

+1 for specifying a parent page.

+1 for specifying a parent page.

we use a workaround for the parent page feature:

Take the link, which is created from the button and the parent page ID can be replaced in this link.

We create a button e.g. with UI Button Macro and put in the link there.

+ 1 for specifying a parent page.

+ 1 for specifying a parent page.

Would be awesome!

C'mon Atlassian: this request is preeeeetty basic and you haven't solved it in four years. 

It would also be very helpful if you could provide other variables in the page title (similar to @currentdate) like: 

• currentweek
• currentweekday{{}}
• currentyear
• currentmonth
• currentday

Would be a helpful addition

Just looking into this today also feel this would be very helpful to my users.

This feature would be very helpful. Please give it a look!

Please give this features a look. It could be very useful to us. 

Parent page would be the most important for our requirements.

Parent Page would be really helpful here. Currently you can define a target space which does not make sense at all when not being able to also define the parent page there imho

Functionality should support predefining a list of labels to be put on the created page.

This functionality would be very helpful in keeping my Knowledge Base structured.   Certain types of information are expected in certain places, such as the meeting notes mentioned previously. 

Please make this available on Cloud! It is such an amazing product but this means I have to comb though pages once a week and move everything where it should be.

Hey @Ian Lee [LLNL] I wanted this as well. I created a user macro that can achieve this until they release something more permanent. Try this:

## Macro title: Parent Page Link
## Macro has a body: No
##
## Developed by: <Your Name>
## Date created: <00/00/0000>
## Installed by: <Your Name>

## @noparams

#if (!$content.getParent())
 <b>No parent page found</b>
#else
#contentLink2($content.getParent() false false)
#end

Any way Atlassian, when is this going to be reviewed?

Being able to specify a "parent page" would be a great improvement to this macro. (Still not possible in Confluence 5.9.7)

Not sure if this helps, but I've been using the "add page" and "add page via form" macros. Both macros let you use a template as a source and

Title fixed (add-page) or custom text (add page via form)
Title prefix and postfix including injectable, dates, etc
set variables $

labels can be defined but don't show up on the new page when a template is used

parent can be set (have not tried this) as follows: The target parent for the new page. Defaults to the current page. If no parent is desired, use a blank value. There are also three special values:
@self - the current page.
@parent - the parent of the current page.
@home - the space home page.

Love this macro (this one actually has @currentDate!), although there are some essential things missing for it to replace our Create Page macro.
Went through the thread a bit, so I presume nothing will be new, but just upvoting some stuff

• specifying location of resulting page
• more parameters in the Title
• adding labels; set or variable "%"
• prefix + postfix
• prompt window to allow injection of custom text into the title.

Adding custom labels for the new page according to macro would be great since it will allow to create separate queries, for example meetings per subject or theme. Also specifying a parent page is critical, this way create from template button can be placed inside the homepage and still not mess the pages hierarchy.

I'm not sure you can - this workaround just uses a static URL and I don't know how to pass variables (e.g. today's date) into it.

With the workaround, how do you specify the variable for the current date in the url so that the current date is included with the page title?

I've just used this workaround in Confluence 5.5 and can confirm it works:

Take the URL from the normal create from template macro and change

&fromPageId=#######

to the id of the desired parent. You can then use a macro such as UI Button from RefinedWiki UI Toolkit to make it look nice

+1 for specifying more variables in the title, especially using variable from the template itself - for example date of meeting in title of meeting notes.

Using @parentTitle as param for the new page will be very useful

This request for a very simple, yet very useful feature, has been sitting here with little-to-no attention from Atlassian for over a year. This is extremely disappointing, because it could have been a quick win for everyone with likely just a couple of hours of someone's work.

In addition to being able to specify more variables in the page title via this macro, it would be great if we could specify built-in variables from inside the template itself - including the ability to define the default page title right in the template - with optional variables (built-in or user-defined) as part of that default title definition as well.

The disadvantage of the macro approach is that people using the "create" menu to select a template won't get the benefits of the default title field.

+1 for user name variable in page title

+ 1 for specifying a parent page.

@piotr,

CONF-29859 was a bug which resulted in all the pages being created at the root of the space, as opposed to a child of the current page. Not sure why it's "related" to this ticket other than it affected the Create from Template macro.

1. Unfortunately the same issue exists in JIRA 6.3.5. For example when I create Meeting Notes based on the built-in template the notes page goes to space root. This obscures the structure of the whole space as this makes it difficult to keep the data readable and structured (the core purpose of using Confluence for me).
2. There exists similar ticket and it is resolved - not sure what it means: CONF-29859, but clearly it suggests that this functionality was present and disappeared for some reason.

Please consider fixing this!

+1 for specifying parent page

Yes, please do this and don't let it sit here any longer. This would provide a lot of flexibility!

+1 for specifying parent page!

Specifying a parent page is a much needed feature for my team too. Considering this parameter is already in the list child page macro I would hope that it wouldn't be too difficult.