How to move pages

[Saira]

I have a page titled WIP in multiple spaces. What I need to do is when a page is published and it's not created under the WIP page of that space, automation should automatically move it under the WIP page in the associated space. 

[Rilwan Ahmed]

Hi @Saira ,

You are correct. When you select "Same space as trigger", the Parent option is greyed out

Workaround: 
Select required Space name and then the Parent page from the dropdown

[Saira]

Thanks but I don't think that's a feasible option - there are dozens and dozens of spaces

[Trudy Claspill]

Hello @Saira 

Have you tried to create this automation rule? Please show us what you have so far.

Reference documentation can be found here:

https://support.atlassian.com/confluence-cloud/docs/what-is-confluence-automation/

You can find the Page Published trigger described on this page:

https://support.atlassian.com/cloud-automation/docs/triggers-in-confluence-automation/#Pages-and-blogs

You can find the Move Page action described on this page:

https://support.atlassian.com/cloud-automation/docs/actions-in-confluence-automation/#Pages-and-blogs

[Saira]

I have created an automation but the problem is, I can't specify the destination parent - it's greyed out - I need to tell it to select a parent page that has 'wip' in it.  

[Tomislav Tobijas _Koios_]

@Saira you would need to select specific space in order to use 'Parent' option/dropdown. 💡 Suggestion would be, probably, to create separate automation rules per space and within each rule you could then select current space and specific parent page.

Cheers,
Tobi

[Saira]

Thanks but I don't think that's a feasible option - there are dozens and dozens of spaces. Why aren't we allowed to use smart variables there? 

[Trudy Claspill]

I searched the public Atlassian backlog for any issues related to this topic and could not find any. I recommend that you open a support case directly with Atlassian to ask that a change request be opened.

As to "why" functionality is not available, as a community of users of the products we don't generally have insights into the "why" of the decisions that Atlassian makes about which functionality to implement. Perhaps in their efforts to provide a minimum viable product for Automation for Confluence Cloud, this functionality has not yet made the cut.