Was also looking for dynamic page creation under trigger or smart value page

Automation on Conf Page creation requires a set path, and this can't be set via smartID variable so that it sit under the page that triggered it

User Case 1
I currently have automations that trigger when a Jira ticket is created, if its summary ends with a specific text string, then a confluence page is created in a specific space

User Case 2

User Case 1 works well for most of the user cases, but there is also a need for a dynamic page tree not fixed, where that tree can be determined via another part of the string.

User Case 3
I have confluence pages that are forms to be completed.

What I was hoping to produce was using tasks/Actions and listening on when certain ones are checked, then create a page under it from a template 

This failed on two accounts

1) The Task/Action IDs not being unique so it failed before it started, despite efforts to remake the tasks

2) The page would need to be created in a fixed place, not under the trigger page

The ugly workaround for this is the create page from template button, but this creates the page without the dynamic heading and you need to then publish the page and return back to the form

So not as clean and efficient as it could be.

User Case 4

When triggered a page is created under a fixed location (all good so far), but also child pages are created under it - essentially a tree template

Expand available Smart Values

Adding the ability to utilise Smart Values across more of Confluence would aid automation greatly.

Fields that should accept smart values but currently do not include:

• Change page owner - Owner
• Publish new page
  • Space
  • Parent page
• Move page

• • Space
  • Parent page
• Copy page

• • Space
  • Parent page
• Look up pages - Author
• Grant space permission - user or group

• Restrict page - user or group

We are currently using Automation for Confluence to pre-populate a tree of project artifacts that are created when a project is created. A parent page is created with a label, and that label triggers the artifacts to be created as child pages of that parent before the label is automatically removed.

Or that's how it would work with this feature implemented. Currently the pages are created at the space root and after the automation is finished I have to move them into their proper hierarchy. It would make things much simpler (and I could think of a lot of other scenarios where this kind of dynamic parent would be useful as well) to have it work as described above.