Dee, thank you for saying that, but you should be able to see that this issue was created about 12 and a half years ago, and if you read through the numerous comments you will see I'm not the first or only one to point that problem out. In light of that, your response was overly unconcerned and blithe. I have seen this problem from Atlassian many times for years. I have been a JIRA admin and tried talking to Product Management there about it years ago, to no avail. One time when I called to report unplanned downtime in the middle of the day, I even heard a party going on in the background. 

monica.bowen I'm dismayed you label me as unprofessional.I disagree.

I saw a comment on a closed ticket for a shipped feature that I saw showed a user having difficulty using/understanding our product. I took responsibility to answer this comment. I took time to test the feature, and to understand the complaints that my customer made about it, I took time to respond thoughtfully and courteously. I have sought clarification of the problem.

For any issues with Confluence, I urge customers to seek the help of our support team at https://getsupport.atlassian.com

Certainly the history of this issue is a LONG saga (and I agree many issues do sit for a long time ...)

but if you read the comments here carefully, you will find it was announced on 2nd Nov 2016 that it was solved in version 6 ... and reading the comments further apparently the qualifier is only on server instances, not cloud instances.

We are still on v5.8.16 so I can't verify it (i.e. we are quite happily still relying on the <<Copy Page Tree>> plugin) -

Refer the section " To copy a page and all its child pages:" on this page in v6.3 documentation   https://confluence.atlassian.com/doc/copy-a-page-139013.html

You're so far off-base. I am a customer of Atlassian's, just like you.

Steven, you need to deal with your co-worker's lack of professionalism in responding to customers. Not attempt to chastise you customers in a manner which is also unprofessional. Many people here have pointed out in multiple comments that this issue has been open for years, and Atlassian has continued to ignore it for years anyway. I have seen this same problem with other Atlassian issues for years. Step up and be a professional. Solve problems for your customers and be courteous about it. That's what your customers are paying you to do.

You're sending your comments to over 400 users by commenting here. If you need support go to https://getsupport.atlassian.com/. This feature request works for most people and if you're having an issue you should follow up the proper channel. This is not a proper venue for venting.

Dee you shouldn't be snarky with your customers about a fix that Atlassian waited a full decade to implement. And now child pages have disappeared from the parent page. I'm guessing Atlassian will try to tell me this is not a bug, it's a feature, because Atlassian has given me that line before, like when they suddenly started truncating dropdown menu lists so that users can't see everything in the list if they don't already know all of the items in the list well enough to type them in.

Hi warrenzhai1,

What are you trying to achieve with your copied pages links? Could you list the steps and expectations you have?

I just ran two tests:

1. I copied a set of pages (to another space) which all contained links to each other (i.e internal linking). The copies I created all had links to each other as I expected.
2. I linked to another page external to the hierarchy. Copied the hierarchy to another space. The copy had a link back to the original space. As expected.

We are thrilled to have delivered this much-awaited, long desired feature. Thanks for your patience.

The copy page and its children option is available.  So it "works". 

However, all the links to pages (even the ones that are copied to the new space) will point to the old space and create a pretty big mess that one has to manually update every page.

Also, I can't believe this issue took 10 years to get a release even though it has the highest number of votes. 

 Regards

Yes, You are absolutely right. We wait for it now for more than 7 (!!!!) years. It's an absolut basic in such a tool !!!

Hi @Brendan McNamara,

Any thoughts on when the feature will become available to Atlassian Cloud users?

Thanks!

Hi rdavis7,

From Confluence 6.0 you will be able to copy a page and all of its child pages to the same or a different space. Our documentation here includes detailed steps for how to do this.

Cheers!

Hi - this issue is noted as resolved, but I'm not sure how to actually do this.  Can I copy a set of pages (parent page and all sub-pages) now?  (whether copying into same Confluence Space or different one?)

abarnes@atlassian.com, was this released to Cloud? Based on https://confluence.atlassian.com/confcloud/copy-a-page-724764871.html it looks like it was not. But if you look in the copy dialog in Cloud, it states that it is copying the page and the children. So the in product text got updated, but not the actual feature.

We would also appreciate it to be available for cloud installations.

I understand the feature is now available to on-prem Confluence installs; however, when will it be added to Confluence Cloud?

Thanks!

I have seen this trend with Atlassian for years now. When I was at a company with a JIRA instance hosted by Atlassian, they were constantly making changes to the UI, often for the worse, such as truncating dropdown menu lists so that non-admin users no longer have any way to see all the items in a dropdown menu list. This often meant that we had to keep re-learning the UI, and I often found that when updates happened, new bugs were introduced which I quickly stumbled upon myself, leading me to believe that the changes had not been thoroughly tested. When, as a JIRA admin, I opened support tickets with Atleassian, the bugs I reported sometimes went for years without being addressed.

Agreed, especially with such a fundamental change to core functionality with the Synchrony system used for collaborative editing I would need considerable time on our test server before I was happy to role this out to our production server.

I completely agree with not moving to Confluence 6 at this stage. In our experience the point releases in 5 since 5.5 have been quite disastrous and going down in quality since. Worse still, communicating with Atlassian support usually results in "we've confirmed this as a bug" which never gets addressed.

Atlassian absolutely have an agenda that no longer focusses on quality.

When we ask to upgrade to v.6.0 the response that we get indicates that Atlassian is holding themselves to a very low standard when it comes to quality assurance for a major release.:

"Since Confluence 6.0 was just released few days ago, Premier Support does not recommend upgrading to that version yet. 

We want to make sure that the new release has ample time to "soak" in the wild, to minimize the chances of running into undiscovered critical bugs after upgrading. While our developers make every effort to roll out new bug-fix releases quickly to remedy critical bugs, enterprise environments often do not have the ability to quickly upgrade. 

This is why we generally will not recommend the bleeding edge versions in favor of less surprises and Confluence stability. Furthermore, Premier Support will not be recommending Confluence 6.0 until the release has undergone a thorough Premier Support review with the Server development team of at least 90 days to insure that all blocking issues are corrected before the product will be recommended to our Premier Clients. This has been agreed to with the server development team to insure that our clients are provided with a stable, enterprise-hardened release.  

Until such time though, our current recommendation stands at the Confluence 5.10.8 release for now. Of course, you can still test Confluence 6.0 in a dev environment, but it's definitely not recommended for the production environment yet."

When will this be available on Confluence Cloud?

This feature is available for preview in the Confluence Early Access Program (EAP) in the lead up to the Confluence 6.0 release.
Check out the milestone release notes for more information and to download the EAP.

When will this be available?

I'm looking forward to having this work.

@Adam Barnes, I think a checkbox saying "copy attachments" would be enough. However, not copying unused attachments would be a nice bonus.

Hi,

Usually most users don't want just copy pages or spaces. They want to make adjustments during the copy process. Here our add-on Page Creator Tree and Space Tree Creator helps. Of course, attachments can be copied too and if needed the name of the attachment can be renamed during the copy process.

Give it a try:

• Page Tree Creator
• Space Tree Creator

Regards,
Stephan Sutter

Hi,

we recently released an update of our Add-On Space Admin for Conflunce, which from our point of view covers most of the requested features in this thread.
Inclucing a nice UI (with drag&drop), coping spaces, pages, attachments (all or non), a detailed view of spaces with a list of all attachments, comments, blog, trash and also we offer a bulk-editor of space-permissions.

So if you like to copy spaces, pages, attachments and so on .. you can do this in space admin the most easy way. And Space Admin is available for Data Center.

Check it out https://marketplace.atlassian.com/plugins/com.decadis.confluence.spaceadmin/server/overview

Please do not hesitate to contact us if you have any questions!

Kind regards
Daniel John

@adam barnes, if one had a really robust image management system then option 2 would be ideal, BUT I suspect most people have a combination of a proper image library and images quickly pasted on to pages. This would make option 2 a bit risky, even though in theory it sounds good.
In the absence of a 'checkbox' option (the scenario people have described as an 'Option 3'), then Option 1 would suffice. If however adding a checkbox option would not overly delay the issue then it would be awesome.

@abarnes I second @andrewdrury in voting for Option 3 - all attachments, used or unused, shown in a checklist with a select-all option. If that is not possible, Option 1 is the next best - option to copy all attachments (used or unused) or no attachments.
For option 3, our use case is similar to many others. As the main site admin and Confluence Evangelist in my organization, I want people to be able to copy existing page hierarchies so they don't have to start from scratch.

@Adam Barnes: We also copy process manuals from one Version to the next. We always need all attachments to be copied, so basically we do not need an option to omit them. If required, we would vote for option 1.

or to put it another way ... if I was Atlassian, rather than developing new functionality themselves, buy the rights off Artemis ... once the bug is fixed

well... funny you should ask ....
the original version we installed in January worked absolutely fine albeit a little "clunky" in a couple of ways but worked fine - particularly as I could de-select individual pages from the tree to be copied.
It has helped me roll out a huge number of tree copies which I couldn't have done otherwise
I am a huge fan as a result

But we recently upgraded to v2.1.0 - its user interface is a little neater ...
"but #1" I can't deselect individual pages from the tree
"but #2" it has problems when there are more than 10 pages in the tree ... they are working on that https://artemis.atlassian.net/browse/CPT-44
I am still a huge fan basically since there is no other way to do it ... I just have to spend a few minutes making sure I can copy the tree in groups of 10 pages or less so one tree may take 2, 3 or 4 groups - I create some dummy pages "aaa", "bbb" .... then group pages into those using Browse>Pages>treeview ... but it works fine and I can easily de-group in the destination Space using Broswe>Pages>treeview

One feature improvement would that the destination parent page listing is "flat" - i.e. it doesn't show as a tree itself so you have to look carefully as to where the parent page is since it is flat by tree structure, not alphabetically

.. but still a big fan taking "5 minutes" to do a tree even with grouping to "small trees"

Hi @Rodney Hughes,

What is your experience with the 'Copy Page Tree' plugin in aspects of server load and system stability? We have a very large enterprise instance and I fear instabilities and other system issues if we provide this feature to all our users.

Well, I don't actually care any more as we got the "Copy Page Tree" plugin - it has the option of selecting copying attachments or not.
But to note I have never NOT copied the attachments and I can't imagine a use case where I wouldn't because any embedded links/images would be broken.
So it depends on Atlassian's own marketing stance.

Note copying pages from one Confluence instance to another instance is not really possible from a simple plugin as proposed here or provided by "Copy Page Tree" - we recently did this but it required our host of BOTH instances to export the XML, do some URL fiddles and the import into the other instance.

@Adam Barnes - I'd vote for Option 1, unless Option 3 is available, which is to have a checklist of all the attachments, so we can (un)check any attachments we don't want to have copied. I appreciate that that might be harder, and would rather have option 1 soon than wait longer for option 3.

Our use case is that we produce project management manuals consisting of Confluence pages with Gliffy flowcharts, text, tables and some images within them. Most of the Pages will have template documents attached (such as a template letter of appointment for an architect) so that the user can create an operational document from it ( such as an actual letter appointing an architect to a particular development). These are in a hierarchy that is usually about 4 but can be up to 6 levels deep. There are about 250 pages in total, I think.

There are three variations of the Master Manual in the same Space. The same set of Pages are replicated in many parts of the 3 variations. When one of these sets of Pages are updated, we need to be able to copy the updated set of Pages / Child Pages (with the updated attachments) from one location to another location within the same space.

But we also host Manuals that we have sold to clients and customised for them on our instance of Confluence, but in different Spaces. So we also need to be able to copy Pages / Child Pages and attachments from one Space to another Space in our instance.

Finally, we sell the Manual to clients who have their own instance of Confluence, either Cloud or Server. So we also need to be able to copy Pages / Child Pages and attachments from our instance to another instance.

And in all this, we need all the hyperlinks between the Pages that we are copying to be retained.

Hope that helps.

@Evgeny Victorov
this is a different usercase i think (creating templates with subpages and attachments; we want that too!)

option 1. sounds best as sometimes not all wanted attachments are displayed on the page itself.
maybe with some separate option to download all attachments if you don't want to copy them.

just my 2cent

Adam, our use case is the following: we create a page with some children, fill them in and then understand it's good enough to be a template. Thus, we want to copy this part of page hierarchy. As this is a template, I'd like to have all the attachments copied - I'd better remove unneeded later than would fix "Unknown attachment" pieces all around.

Your input requested:
We are currently working on implementing this feature and have a consideration to make regarding the use case(s) driving the copying of attachments. We currently have an option to copy all/none of the attachments for the page tree being copied. The concern around copying NONE of the attachments is that some images/multimedia/documents will not be copied resulting in users 'losing' this page content at the destination.
Please comment on the preferred use of this option:
1. Option to copy All attachments / No attachments (e.g. 'Unknown Attachment' on destination pages)
2. Option should ALWAYS copy content which is used (e.g. images/mp4/doc/ppt/pdf) on the page and only skip attachments which are unused by any of the pages in the tree to be copied.
3. Other
Please describe your use case and any background relating to this preference to help us understand your individual needs?

Thanks Michael,
You are quite right. I've corrected the example.

Hi Mark,

is the example correct? The marked pages do not have "v2" in their title.

Good to hear that ScriptRunner can do this, too. Looks like it is indeed no voodoo. But still, this should be core functionality of Confluence.
We do have ScriptRunner licensed, btw.

Hi, we've very recently released a new add-on ScriptRunner for Confluence that allows you to copy a page hierarchy (including attachments).
This is available as a built-in script - Copy a page tree and looks like this:

You'll see from the example that it includes the ability to copy pages to the same space and replace versions (say "v3" with "v4") which would be useful if you have product documentation.

I wrote a small script for copying page tree, so maybe it would help someone: https://github.com/grundic/confluence-page-copier

Now we have 2016. Means this ticket is open since 11 years.
Means we pay 32k$ per year not be able to copy pages successfully.
Nice

Hi Adam,
You know there are 865 people that receive an email each time you update this label right?

Normand

Thank you Rodney and Bruno!
We are a Cyrillic-culture company so looks like we'll have to wait for Atlassian to add the "Copy with children" functionality.

Hi, it's a very useful tool, I use it a lot for our documentation spaces (Cloud version) when we need to issue a new version of our products. There's a minor issue you need to take into account: it does not keep the order of the pages you defined. You will have to manually reorder pages using the "View in hierarchy" option once copied. I asked the developer for an update but I think this tool will not be updated anymore. Please note it will fail if some pages are not allowed to be read by the "Copy Page Tree" account and also if you use Cyrillic characters in attachment names (screenshots for example).
Hope this helps

correct - I selected a page within the Space and copied that and automatically applying name changes "yy" to "16" - two screen shots below from the same Space - the Copy Page Tree macro and the same Space navigation afterwards

@rgh1 clarification: did it copy a specific page with its children within the same space? (not the whole space copy, not withing other space)

@rgh1 I might add a note that the described functionality could be needed for others - as AFAIK Copy Page Tree copies the whole space but not the specific pages within the same space.

Ok - thanks for letting us know .... do you have some sort of status change for this request as "ignored" or "maybe".
We have now chosen to go with Copy Page Tree plugin as mentioned by a few others above - that does enough of what we need.

rgh1 I made an update the workflow which affected every CONF ticket. I'm afraid I have no particular involvement or insight into this feature request..

There was a recent comment on a related request from a Confluence Product Manager. The update says "This development work is not currently in the roadmap, but it is being included for future planning"

@Mark Hrynczak or @Charles Miller
Since the Atlassian CEO has not answered my letter I posted to him in December, and you as the last person who "touched" this request when I just checked, could you please answer these questions for us all please ......
Q1: What date will we be able to use a standard Confluence tool to Copy a page and all its child pages (including content but not necessarily attachments)?
Q2: What date will we be able to do it including any attachments?

If you cannot provide dates as yet, please advise if it is on the "roadmap" at all.
After 10 years of asking for this fundamental feature, I think we deserve the honesty from Atlassian tell us if there is no intention to do this.

I agree with both of you. That should be a system function.

I agree with Michael.

I agree with Gilbert,

As good the plugin could be, this should be the responsability of Atlassian.
I cannot build a Wiki Site and keep buying plugins and plugins and plugins....This is nonsense.

Atlassian business model should not rely on the purchase of plugins.
In the end, I get a tool that costs $ 16,000 and a plugin suite for $ 60,000. This is no longer possible.

What should be a good solution is:
A good plugin should be bought by Atlassian and proposed for free for holders of a valid license.

No offence Daniel, but we have been buying too many plugins for simple functionality that should be part of the core of Confluence.

Michael

Seemed to be a good tool. But out of my view, it should be a standard of Confuence to copy a page hierarchy as a content management system.
Sorry. To pay 1600 $ for a 2000 people instance is to expensive.

Dear participants,

We decided to resolve this issue by ourself and developed a confluence add-on for organizing spaces and pages.

You can copy full page hierarchy with attachments, comments and permissions. You can also copy a complete space with all its pages, comments, attachments etc. It is also possible to select a subset of subpages to copy.

Here you can find the Space Admin add-on for Confluence:

https://marketplace.atlassian.com/plugins/com.decadis.confluence.spaceadmin/server/overview

To see all features have a look at our documentation:

https://decadis.atlassian.net/wiki/display/SPAD/Space%20Admin

Enjoy!

Daniel John,
Decadis

We are urgently waiting for this!

842 votes... this is mind-boggling. It can't be that complicated, can it??

Dear Confluence developers - please provide an answer to this question .....

When, i.e. give a date, will I be able to copy a set of pages and their children hierarchy from one Space to another? i.e. how much longer do we have to wait?

I don't need to bring attachments across - in fact I don't want to bring any attachments so perhaps a staged release of a feature to copy pages and a subsequent development release to bring the attachments??

Our Use-Case is that as we create new Spaces for different groups of members we want to create the Spaces with a standard initial set of page structures (depending on which type of group it is, they have different structures) with their standard page text/links etc (no attachments involved, but there may be standard URL hyperlinks to other web pages)

This issue was created in 2005 - yes it has reached its 10-year anniversary.
On its 8th anniversary in October 2013 it had 547 votes
Now on its 10th anniversary in Nov 2015 just 2 years later it has 837 votes (that is a 50 % increase in the last 2 years alone)
It STILL shows as "Unassigned"

Your standard documentation still advises that you can't do it so clearly you know about the need:
https://confluence.atlassian.com/display/CONFKB/How+to+copy+or+rename+a+space+in+Confluence

So as I asked in May 2014: "Can you please give us a time frame that we could expect this feature to be available - 1 month, 3 months, 1 year, more? ...."
I never received an answer to that!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

And as @Richard Kalas also said in May 2014 " Let's hope it doesn't take until 2015 for this request to be addressed ! It really should be basic functionality."
Well I guess that hope has gone by the wayside .... but no new hope is evident!!

I add my vote for this feature. I'd also like this added for the include page macro. When I include pages I'd also like to be able to add all children pages

Moving works but not copying.

Question for Atlassian -
I had to move branch of pages from one space to another.
Got ready for boring work - printed out a list of pages as a check list.
Started with root page and all branch has moved to another space!
PS: I am on Confluence 5.9.0-OD-58-008

Now question -
This function is implemented, why not to resolve this 10 years old issue?

No, nothing in the log, also after few seconds of the request I get the error message, so I don't suspect time out error.

Does the server log give you any clue of the error or does it just time out?

I have tried and it did not work. The page hierarchy is about 1.5 G when I exported the page hierarchy, but I'm unable to restore the backed up page in a different space. So I found this feature, it did not work!

@Mustafa Abusalah: Did you try it or just refer to the Marketplace Ad? It is working on our side with 5.7.1.

This is not working on 5.7

Hey Agnes,

We have used this feature a few times and it is working great so far.

Thanks!

Please bear in mind what has been built so far is really just the first revision and is feature light.

Hi Agnes,

here is a long-awaited improvement that should have been introduced with a fireworks
Thanks a lot.

I'll test it in the day ...

Michael

Hi all, I have built a BETA release of a copy page hierarchy plugin that is compatible with Confluence 5.6. Please try it out! Any feedback would be much appreciated.

https://marketplace.atlassian.com/plugins/com.atlassian.confluence.plugins.confluence-copy-page-hierarchy-plugin

Cheers,
Agnes

Same as users above me mentioned. This would be a must-have-feature, eg. if you have new contract bidding with several companies and all commenting is done for prices and requirements in Confluence. All companies are in cloned trees and restricted so that they can't see each other --> takes lots of time to copy whole tree for 3-10 times.

Same exact need as the user above me. We have created templates and need to copy the parent page with all child pages.

Also support this feature. As with Tyson Burke, we have page structures as templates so need to be able to copy parent AND child pages in the name of efficiency.

I agree with the many sentiments already posted - this feature would be HUGE for our company since we often like to re-use page structure so we can take advantage of templates that include nested content etc.
Can't wait fo this to get on the roadmap and actually be implemented!

Absolutely a good feature for Confluence, need it right away.

andreasplattner a workaround you could try to copy across the page content only:

• On the original page, use Tools->View Source, then select and copy all (Ctrl+A, Ctrl+C)
• In a new page editor, paste in the clipboard content, and save

To admit I'm a bit lost here, coming from the issue to chose whether attachments should be copied alongside their page or not.
For us it is very annoying having to remove a bunch of attachments every time a page is copied. This is especially painful when you do this on a regular basis like with retrospectives or training material. Please fix this. Don't think this ultimately has to happen alongside a hierarchy copy, but I would appreciate the very basic copy operation to support this!
Thanks

Again from my side, I remarked it 5 years ago. This is a real basic feature of all homepage platforms, all operating system, explorers a.s.o.
But as mentioned above, Atlassian don't talk sometime long time in this ticket/feature system.
The same was it with the trash item. For years nothing and then a plugin you can pay for. We did not. We decided to make our own easy solution.
The best way sometimes would be to leave Atlassian Products, because same behavior is in JIRA and Stash tickets.
Sorry, Atlassian, to say, but why do you have this system, when you don't use it correctly????
Assignee: who? Nobody works at all for Atlassian? What is going on in your US and Australien place? Do you prefer making new videos with new feature which will not be used, because customers turn away from Atlassian? Do you create new features with new problems, without solving old.
We say to our customers: "Sorry, we have no time to solve your actual problem, we are ongoing to create new problems for you" That's software. That's a world, customers test and suffer, pay money for this, for licences, for maintenance, but the supplier doesn't care about it. He is happy to get money.

So go on this way. But you will notice, that more and more customers will leave ...

Atlassian, PLEASE communicate with users as to your intention with this feature. Let us know if you are going to build in this very basic feature, or not (I hope the answer isn't 'because we now have a plug-in').

oh please no ... i can already see it: Atlassian will tell us this will not be fixed because there is now a plugin to do so. I certainly wont buy that plugin but will instead tell everyone i know not to use Atlassian Products from now on, because of basic functionality that does not get implemented for 10 YEARS despite hundreds of user votes. Instead Atlassian just waits for someone to make a commercial Plugin to alleviate the pain of their users and as sad as it might sound, they might get away with it.

I mean please ... copying of a page hierarchy, how hard can it be?

Not built-in and not free, but there is now an add-on which provides this capability for OnDemand instances.

https://marketplace.atlassian.com/plugins/com.nurago.confluence.plugins.treecopy#cloud

Hello,
we're using Confluence OnDemand and we created a documentation with several child pages and now we need to reuse this documentation several times (for different operating systems, different features, etc...) so we really need the copy page hierarchy option. Can't believe we will have to copy each page one by one or perform complicated operations to export to XML, change space name, import to another space, without being sure to retrieve everything, then move pages... and repeat this multiple times....
I found some explanation here:
https://confluence.atlassian.com/display/CONFKB/Copy+or+Rename+a+Space+in+Confluence

Hope this issue will not have its 10th anniversary...

I don't know what's more confounding: the fact that this issue has been open for so long or that it is apparently not assigned to get fixed! Come on, Atlassian - it's a basic and obvious content management tool that most systems offer as a basic. Please address this urgently - or at least post an explanation of why it isn't being addressed.

Let's hope it doesn't take until 2015 for this request to be addressed ! It really should be basic functionality.

I was trying to duplicate a page+children hierarchy just now and, frankly, could not believe my eyes that the function does not exist. Isn't this a tool to build and manage a hierarchic structure...?
Then the Help page advised me to add a vote to https://confluence.atlassian.com/display/CONF53/Copying+a+Page to "see this improvement". If leaving comments is the way to "vote", here you go: ADD. MY. VOTE.
Then I checked this page and found that on 27 Feb 2015, the issue will have its 10th Anniversary!

Hey Atlassianers or Atlassianists, wouldn't that be a great time to go live with a fix?

This is, hm, so obvious to implement. If not for your users (who clamored for nine years w/o being heard), just for the sake of elegance.
(Peace. Sorry about my sarcasm.)

@Agnes Ro
back on 4th October I noted above that there were 547 votes for this
You replied a few minutes later that you were trying to get this on to the roadmap
Six months later, there are now 640 votes (and 285 watchers)

Can you please give us a time frame that we could expect this feature to be available - 1 month, 3 months, 1 year, more? ....

There seems to be two requirements for this
1. Copy a page and its children within the same Space, with the option to include attachments or not
The trick here is of course that all the pages have to have unique names within the Space so when the children, grandchildren, great_grandchildren ... pages are copied they all have to be renamed by some means but at least they can each default to "copy of ..." and then the users manually rename them

2. Copy a page and its children to another Space, with the option to include attachments or not
This still needs to consider that the new Space may already have pages with the same names as the source Space so "copy of ..." is still probably the way to go

But if it was REALLY clever and useful, then for each page that has a conflict name, a pop up table of some sort allows you to nominate the new names for the copied pages as you go - that would save a manual "search and correct" hassle afterwards ....

Definitely support this new feature, it's something that we sorely miss.

Hi,

Adding in my vote as another paid subscriber to Confluence and JIRA. It is a little shocking that this basic functionality is not available. Please move forward with fixing this ASAP. If a page can already be copied, im sure there should be a manageable way to get this going quickly.

Yes, just use Log in and click on "Create an account".

Bob, I will but it looks like I need a login to access the Create Issue screen.

dev8: Best to open an issue and we can deal with any problems there.

I've been following this ticket for years now and I have to agree with other users that the lack of an officially sanctioned method via the GUI is baffling. This is by far the most voted/watched ticket I see for Confluence.

Exporting as XML and doing search and replace is an insanely dumb way to do it. You leave all sorts of non-technical users up to potentially making breaking changes. Forget about doing it programmatically, now you need to hire a developer to do something that should be available out of the box.

Using the Copy Space plugin is nice, but it is not supported by Atlassian. Users want something that is supported so that we can confidently and securely update spaces.

At my old software company we made a top ten list every year of our user's most requested features. Every year we tried to make those things happen. Some took years to complete, but they got done. Leaving this on the table for nine years is unacceptable.

@Bob, do you have any sample scripts? When we try and use copypage for a rather large page hierarchy it fails because its trying to create pages with the same name in the same space. Is there a way to add a tag to the page title to make them unique during the copy process? If we rename the page before or after copypage it still fails because it has to create the page before changing the name. I'm all for automating this via Bamboo but so far so bad.

While we all agree it would be nice to have this as part of the base UI, it is not a show stopper for doing the kind of thing you are talking about. It has been mentioned a few times earlier in this thread, but it is probably worth mentioning again. From a software development perspective, you should be thinking of automating this in any case and Confluence Command Line Interface has support for copyPage and related actions that make this a one liner. More over, it can copy to a different confluence if necessary. Even better, you can easily add a CLI task in your Bamboo builds to do it as a step of your build automation.

I would like to support the urgent need for development of this functionality. Working in the Software Development industry, we would prefer to retain a 'copy' of our preproduction documentation (so that we can continue to work on it) and 'release' the approved version as a copy (of the page and its child pages) to a Production space. The inability to easily create a copy of a page hierarchy is a major constraint.

Fair comment.