• 19
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      It would be great if in addition to moving a page and all its children, you could instead create a copy in a different space.

      Workaround:
      Some Space Clone options can be found at How to copy or rename a space in Confluence

        1. ChildPagesHaveDisappearedfromParentPage.png
          ChildPagesHaveDisappearedfromParentPage.png
          25 kB
        2. ChildPagesHaveDisappearedfromParentPages2.png
          ChildPagesHaveDisappearedfromParentPages2.png
          27 kB
        3. copy-page-hierarchy.png
          copy-page-hierarchy.png
          141 kB
        4. copy-page-tree.png
          copy-page-tree.png
          149 kB
        5. screenshot-1.png
          screenshot-1.png
          10 kB
        6. screenshot-2.png
          screenshot-2.png
          6 kB
        7. Screen Shot 2017-02-16 at 3.28.09 PM.png
          Screen Shot 2017-02-16 at 3.28.09 PM.png
          60 kB

            [CONFSERVER-2814] Copy page hierarchy (including attachments)

            NazariyL added a comment -

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

            NazariyL added a comment - @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:

            Regards,
            Stephan Sutter

            EPS Software Engineering AG added a comment - 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

            Daniel John added a comment - 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.

            Helen Gosper added a comment - @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.

            Prabha Dias added a comment - - edited

            @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.

            Prabha Dias added a comment - - edited @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.

            Michael Roßmann added a comment - @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

            Rodney Hughes added a comment - 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"

            Rodney Hughes added a comment - 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.

            Jens Kasperek (Bosch GmbH) added a comment - 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.

            Rodney Hughes added a comment - 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.

            Andrew Drury added a comment - - edited

            @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.

            Andrew Drury added a comment - - edited @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.

            MK added a comment -

            @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

            MK added a comment - @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.

            Eugene Victorov added a comment - 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?

            Adam Barnes (Inactive) added a comment - 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.

            Mark McCormack (Adaptavist) added a comment - 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.

            Michael Roßmann added a comment - 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.

            Mark McCormack (Adaptavist) added a comment - - edited 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.

            grundic added a comment -

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

            grundic added a comment - 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

            Christian Sprenger added a comment - 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

            Normand Carbonneau added a comment - 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.

            Evgeny Victorov added a comment - 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

            Bruno Miretti added a comment - 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

            Rodney Hughes added a comment - - edited

            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

            Rodney Hughes added a comment - - edited 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)

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

            Copy Page Tree did create a page and its children within the same Space for me as well as into another Space.

            Rodney Hughes added a comment - Copy Page Tree did create a page and its children within the same Space for me as well as into another 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.

            Evgeny Victorov added a comment - @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.

            Rodney Hughes added a comment - 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 (Inactive) added a comment - 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"

            Rodney Hughes added a comment - - edited

            @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.

            Rodney Hughes added a comment - - edited @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.

            Mustafa Abusalah added a comment - I agree with both of you. That should be a system function.

            I agree with Michael.

            Andrew Drury added a comment - I agree with Michael.

            Michael Regelin added a comment - - edited

            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

            Michael Regelin added a comment - - edited 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.

            Gilbert Stein added a comment - 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

            Daniel John added a comment - 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

            Thomas Schubert added a comment - - edited

            We are urgently waiting for this!

            Thomas Schubert added a comment - - edited We are urgently waiting for this!

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

            Birgit Grossmann added a comment - 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!!

            Rodney Hughes added a comment - 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!!

            Ben added a comment -

            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

            Ben added a comment - 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

            BenoitP added a comment -

            Moving works but not copying.

            BenoitP added a comment - Moving works but not copying.

            SL added a comment -

            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?

            SL added a comment - 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.

            Mustafa Abusalah added a comment - 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?

            Jan-Peter Rusch added a comment - 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 added a comment - 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.

            Jan-Peter Rusch added a comment - @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

            Mustafa Abusalah added a comment - This is not working on 5.7

            Terry Pettitt added a comment - - edited

            Hey Agnes,

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

            Thanks!

            Terry Pettitt added a comment - - edited Hey Agnes, We have used this feature a few times and it is working great so far. Thanks!

            Agnes Ro added a comment -

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

            Agnes Ro added a comment - 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

            Michael Regelin added a comment - 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

            Agnes Ro added a comment - - edited

            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

            Agnes Ro added a comment - - edited 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

            Mikael Kuisma added a comment - - edited

            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.

            Mikael Kuisma added a comment - - edited 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.

            Terry Pettitt added a comment - 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.

            Bronwyn Meadows Smith added a comment - 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!

            Tyson Burke added a comment - 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.

            Admin Account added a comment - 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

            Mark Hrynczak (Inactive) added a comment - 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

            Andreas Plattner added a comment - 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 ...

            Gilbert Stein added a comment - 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').

            Helen Gosper added a comment - 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?

            Johannes Renoth added a comment - 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

            Jonathan Hult added a comment - 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...

            Bruno Miretti added a comment - 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.

            Helen Gosper added a comment - 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.

            Richard Kalas added a comment - 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.)

            Gyuri Juhasz added a comment - 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.)

            RodneyH added a comment - - edited

            @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 ....

            RodneyH added a comment - - edited @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.

            Paul Bindokas added a comment - 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.

            Michael Bengston added a comment - 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.

            Bob Swift added a comment -

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

            Bob Swift added a comment - Yes, just use Log in and click on "Create an account".

            Epic River added a comment -

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

            Epic River added a comment - Bob, I will but it looks like I need a login to access the Create Issue screen.

            Bob Swift added a comment -

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

            Bob Swift added a comment - 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.

            Thomas Sherman added a comment - 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.

            Epic River added a comment -

            @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.

            Epic River added a comment - @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.

            Bob Swift added a comment - - edited

            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.

            Bob Swift added a comment - - edited 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.

            David Gilchrist added a comment - 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.

            Pete Woolley added a comment - Fair comment.

            Michael Roßmann added a comment - - edited

            How much votes does a ticket need to even get on an agile board at Atlassian?

            Michael Roßmann added a comment - - edited How much votes does a ticket need to even get on an agile board at Atlassian?

            If it's that simple im wondering why atlassian wasn't willing/able to provide an implementation in the last nine years...

            Dirk Lachowski added a comment - If it's that simple im wondering why atlassian wasn't willing/able to provide an implementation in the last nine years...

            Normand Carbonneau added a comment - - edited

            Kevin, actually, this is possible to do what you describe in your example. What we do in our case is the following:
            1. Let's say you have Software A - Version 1, this is the name of your Space. Let's assume your space have a Space Key = SOFTAV1
            2. Export this entire Space
            3. Unzip the files that were exported
            4. Edit the following files : entities.xml and exportDescriptor.properties any do a search and replace of the Space Key (Replace SOFTAV1 by SOFTAV2 for example)
            5. Zip the edited files
            6. Do a Space Import with this zip file

            You now have an exact copy of your Space. Simply rename your Space for example to Software A - Version 2 and you are ready to edit the pages of your new Space to reflect the changes in the new version of your software.
            Finally, we provide a Main Documentation Page that lists all versions of the sofware. Each link points to a different Space, depending on the version.

            Hope it helps!

            Normand Carbonneau added a comment - - edited Kevin, actually, this is possible to do what you describe in your example. What we do in our case is the following: 1. Let's say you have Software A - Version 1 , this is the name of your Space. Let's assume your space have a Space Key = SOFTAV1 2. Export this entire Space 3. Unzip the files that were exported 4. Edit the following files : entities.xml and exportDescriptor.properties any do a search and replace of the Space Key (Replace SOFTAV1 by SOFTAV2 for example) 5. Zip the edited files 6. Do a Space Import with this zip file You now have an exact copy of your Space. Simply rename your Space for example to Software A - Version 2 and you are ready to edit the pages of your new Space to reflect the changes in the new version of your software. Finally, we provide a Main Documentation Page that lists all versions of the sofware. Each link points to a different Space, depending on the version. Hope it helps!

            We would like user guides organized in many child pages and subpages. With each new version of our software, we plan to publish a similar user guide with the addition of new features. It would be very helpful to be able to copy the page with all child pages included so the next version of the user guide will be easier to complete.

            Kevin Hatcher added a comment - We would like user guides organized in many child pages and subpages. With each new version of our software, we plan to publish a similar user guide with the addition of new features. It would be very helpful to be able to copy the page with all child pages included so the next version of the user guide will be easier to complete.

            This feature is very much necessary

            shamil shamil added a comment - This feature is very much necessary

            RodneyH added a comment -

            @ Beth Whittle
            glad to hear it is getting some attention - we are all desperate ....

            Whilst you are trying to get things onto the Roadmap, could you look at one other issue which has two entries,
            https://jira.atlassian.com/browse/CONF-7371 has 38 votes
            https://jira.atlassian.com/browse/CONF-26696 has 66 votes
            Also a desperate requirement ... dating back to 2006 ! and it only needs a fourth date field to the three already provided .... surely not that hard???

            RodneyH added a comment - @ Beth Whittle glad to hear it is getting some attention - we are all desperate .... Whilst you are trying to get things onto the Roadmap, could you look at one other issue which has two entries, https://jira.atlassian.com/browse/CONF-7371 has 38 votes https://jira.atlassian.com/browse/CONF-26696 has 66 votes Also a desperate requirement ... dating back to 2006 ! and it only needs a fourth date field to the three already provided .... surely not that hard???

            +1 for OnDemand

            Beth Whittle added a comment - +1 for OnDemand

            Agnes Ro added a comment -

            Hi all,

            I am currently trying to get this scheduled on the roadmap. Yes we do look at tickets, especially highly voted ones. We appreciate your feedback and totally understand your frustration. Any updates on this feature will be made to this ticket.

            Cheers,
            Agnes

            Agnes Ro added a comment - Hi all, I am currently trying to get this scheduled on the roadmap. Yes we do look at tickets, especially highly voted ones. We appreciate your feedback and totally understand your frustration. Any updates on this feature will be made to this ticket. Cheers, Agnes

            RodneyH added a comment -

            There are now 547 votes for this feature since the request was created in 2005!!!
            Is anyone from Atlassian looking at this? How many votes are needed before it gets fixed?
            Everyone is wasting so much time complaining about this and doing things one page at a time!!!

            RodneyH added a comment - There are now 547 votes for this feature since the request was created in 2005!!! Is anyone from Atlassian looking at this? How many votes are needed before it gets fixed? Everyone is wasting so much time complaining about this and doing things one page at a time!!!

            Cynertia added a comment -

            +1

            Cynertia added a comment - +1

            Basic stuff that MUST be implemented !

            Richard Gjøvik added a comment - Basic stuff that MUST be implemented !

            Yes, I'm still surprise that this functionality is not yet implemented in Confluence.
            It is a basic must have. Every weeks, customers ask me to copy a tree of a space into another.

            The bad way is to export an xml tree of a space into anoter. But this is so complicated and so frustrated.
            Hey Atlassian guys, time to deal with this ... old "new feature"

            Michael

            Michael Regelin added a comment - Yes, I'm still surprise that this functionality is not yet implemented in Confluence. It is a basic must have. Every weeks, customers ask me to copy a tree of a space into another. The bad way is to export an xml tree of a space into anoter. But this is so complicated and so frustrated. Hey Atlassian guys, time to deal with this ... old "new feature" Michael

            So what is the status of this?
            Did Atlassian Add this feature to the new Confluence?
            What is the status? Did Atlassian add this simple feature?

            James Allen added a comment - So what is the status of this? Did Atlassian Add this feature to the new Confluence? What is the status? Did Atlassian add this simple feature?

            Why? Why is this not implemented yet? This is B A S I C stuff!

            Johannes Renoth added a comment - Why? Why is this not implemented yet? This is B A S I C stuff!

            As a relatively new user of Confluence, authoring several slightly different versions of a technical manual for different clients I expected to see this feature already installed. We urgently need a half-way house between copying an entire space and individual pages. I have many pages with 4 or 5 layers of children underneath them, maybe totalling 10 or 15 child pages in total. Copying them all individually is REALLY inefficient when I should be able to copy them en bloc.

            I'm rather gloomy about this important feature being introduced, though, as I see that it's 8 years........yes, 8 years!......since it was requested. Is there a target date for this feature to be introduced, please, he asked, forlornly.

            Thx

            Andrew Drury added a comment - As a relatively new user of Confluence, authoring several slightly different versions of a technical manual for different clients I expected to see this feature already installed. We urgently need a half-way house between copying an entire space and individual pages. I have many pages with 4 or 5 layers of children underneath them, maybe totalling 10 or 15 child pages in total. Copying them all individually is REALLY inefficient when I should be able to copy them en bloc. I'm rather gloomy about this important feature being introduced, though, as I see that it's 8 years........yes, 8 years!......since it was requested. Is there a target date for this feature to be introduced, please, he asked, forlornly. Thx

            Richard, what you described sounds to me like a bug. It could also be related to permissions but that seems unlikely as the content was originally created in his personal space (was it not?).

            So what can happen when you move a top-level page is that you have permissions to edit the top-level page and some lower-level pages but not all. If there are restricted pages that the user does not have permission to edit, they cannot be moved. In this case those pages become orphans in that space. But only the person or group that had permission to view those restricted pages originally can find them after the move operation.

            I would (ask the system administrator to) perform a database query looking for the missing pages. It has happened to us that restricted pages have become inaccessible to all but the system administrator because the user or group that had view permissions had been renamed in the LDAP. It's also worth noting that even a system administrator cannot see restricted pages in searches or any browse modes, and links to them appear broken. You can however still access them with the direct URL, if it is known to you. And you can always search for the title in the database.

            But like I said, this scenario seems unlikely as the content was from a personal space. The author should always be able to find the content he/she created. So this seems like a bug. But I have never had content simply 'disappear' as in disappear from the database as well - only disappear from view because of fudged permissions.

            Deleted Account (Inactive) added a comment - - edited Richard, what you described sounds to me like a bug. It could also be related to permissions but that seems unlikely as the content was originally created in his personal space (was it not?). So what can happen when you move a top-level page is that you have permissions to edit the top-level page and some lower-level pages but not all. If there are restricted pages that the user does not have permission to edit, they cannot be moved. In this case those pages become orphans in that space. But only the person or group that had permission to view those restricted pages originally can find them after the move operation. I would (ask the system administrator to) perform a database query looking for the missing pages. It has happened to us that restricted pages have become inaccessible to all but the system administrator because the user or group that had view permissions had been renamed in the LDAP. It's also worth noting that even a system administrator cannot see restricted pages in searches or any browse modes, and links to them appear broken. You can however still access them with the direct URL, if it is known to you. And you can always search for the title in the database. But like I said, this scenario seems unlikely as the content was from a personal space. The author should always be able to find the content he/she created. So this seems like a bug. But I have never had content simply 'disappear' as in disappear from the database as well - only disappear from view because of fudged permissions.

            This should also be extended to cater for the Move function also. A colleague recently discovered this issue when he performed a Move on a page hierarchy in his personal space to a project space. He moved the top level page and on discovering it hadn't also moved the children went back to his personal space and couldn't see the orphaned pages.

            I have subsequently looked for the orphaned pages and could not find them. This caused an entire piece of work to have to be redone, and many hours wasted. Worse, however, is the perceptual damage this caused internally to the introduction of Confluence as a robust business platform.

            Kind regards.

            Richard Kalas added a comment - This should also be extended to cater for the Move function also. A colleague recently discovered this issue when he performed a Move on a page hierarchy in his personal space to a project space. He moved the top level page and on discovering it hadn't also moved the children went back to his personal space and couldn't see the orphaned pages. I have subsequently looked for the orphaned pages and could not find them. This caused an entire piece of work to have to be redone, and many hours wasted. Worse, however, is the perceptual damage this caused internally to the introduction of Confluence as a robust business platform. Kind regards.

            Stephan Vollmer added a comment - - edited

            I wonder how many more votes are required for this feature to get implemented.

            I tried the Copy Page Tree plugin, but it does not work if a page contains attachments.

            Stephan Vollmer added a comment - - edited I wonder how many more votes are required for this feature to get implemented. I tried the Copy Page Tree plugin, but it does not work if a page contains attachments.

            If this feature were ever implemented, a simple "include children" checkbox would be a nice option to have when copying a page.

            Greg Kullberg added a comment - If this feature were ever implemented, a simple "include children" checkbox would be a nice option to have when copying a page.

            In lieu of having native functionality, we've found the Copy Page Tree plugin to solve most of these issues: https://marketplace.atlassian.com/plugins/com.nurago.confluence.plugins.treecopy

            Alasdair Ross added a comment - In lieu of having native functionality, we've found the Copy Page Tree plugin to solve most of these issues: https://marketplace.atlassian.com/plugins/com.nurago.confluence.plugins.treecopy

            I have several project management business cases in using the copy child pages feature would be useful in creating new Project Management Plans (subpages) from an existing project (Page with numerous child pages)

            Richard Dumm added a comment - I have several project management business cases in using the copy child pages feature would be useful in creating new Project Management Plans (subpages) from an existing project (Page with numerous child pages)

            I've only started using Confluence at the start of this year and I'm desperate for this feature. I feel sorry for the guy who has been waiting 8 years for it...

            Sarah Meldrum added a comment - I've only started using Confluence at the start of this year and I'm desperate for this feature. I feel sorry for the guy who has been waiting 8 years for it...

            I am also waiting for this issue to be solved, and I am using On-Demand. My opinion is that when there are a few hundred votes on an issue, we should not rely on third party plugins, but we should rely on the company we put our trust and money in, Atlassian.
            We should ALWAYS think about On-Demand solution as this is the ONLY one that will be fully supported by Atlassian. Third party plugins will never be safe when Atlassian release a new version, except some major plugin partners, like Tempo, Balsamiq, etc...

            Another point I would like to be addressed by Atlassian, is the priority of issues... In SCRUM, we prioritize the backlog, and then take the top X stories and assign these to the next sprint. All the new changes Atlassian brought in the UI recently are really great, but by no means these were a higher priority than other issues with 400-500-600 votes.
            One of the best quality required for a Product Owner is to know what customers need and what gives immediate added value to customers in their day to day work. When customers are telling you that they desperately need a feature (Copy page hierarchy, hiding time tracking from customers, renaming a user group, etc...), please listen to your customers, they are the reason why Atlassian exists.

            Thanks.

            Normand Carbonneau added a comment - I am also waiting for this issue to be solved, and I am using On-Demand. My opinion is that when there are a few hundred votes on an issue, we should not rely on third party plugins, but we should rely on the company we put our trust and money in, Atlassian. We should ALWAYS think about On-Demand solution as this is the ONLY one that will be fully supported by Atlassian. Third party plugins will never be safe when Atlassian release a new version, except some major plugin partners, like Tempo, Balsamiq, etc... Another point I would like to be addressed by Atlassian, is the priority of issues... In SCRUM, we prioritize the backlog, and then take the top X stories and assign these to the next sprint. All the new changes Atlassian brought in the UI recently are really great, but by no means these were a higher priority than other issues with 400-500-600 votes. One of the best quality required for a Product Owner is to know what customers need and what gives immediate added value to customers in their day to day work. When customers are telling you that they desperately need a feature (Copy page hierarchy, hiding time tracking from customers, renaming a user group, etc...), please listen to your customers, they are the reason why Atlassian exists. Thanks.

            Hi @Chris, there are plenty of workarounds listed on this very page. If you browse through the comments, you'll find no less than four plugins that will help you accomplish your task (Copy Space, Copy Page Tree, Copy Partial Space, Archiving Plugin) as well as a command line scripting tool that can, among other things, copy a page with its children to another space.

            But perhaps you are using OnDemand. In that case I'm afraid that there is no cure to your problem. But if you are, you should mention that in your complaint.

            Hope this helps.

            Deleted Account (Inactive) added a comment - Hi @Chris, there are plenty of workarounds listed on this very page. If you browse through the comments, you'll find no less than four plugins that will help you accomplish your task (Copy Space, Copy Page Tree, Copy Partial Space, Archiving Plugin) as well as a command line scripting tool that can, among other things, copy a page with its children to another space. But perhaps you are using OnDemand. In that case I'm afraid that there is no cure to your problem. But if you are, you should mention that in your complaint. Hope this helps.

            OMG - I just saw this has been in the pipeline for 8 years, almost 500 customers want it - what is Atlassian doing? failing to listen to customers. Looks like NO chance of seeing this anytime soon. Does anyone have a workaround? I have a document that needs a full revision that is spread across 50 pages. Bugger me if I'm going to manually copy each page to work on the new draft. !!!!! I'm now regretting moving our documentation to Confluence.

            Chris Kent added a comment - OMG - I just saw this has been in the pipeline for 8 years, almost 500 customers want it - what is Atlassian doing? failing to listen to customers. Looks like NO chance of seeing this anytime soon. Does anyone have a workaround? I have a document that needs a full revision that is spread across 50 pages. Bugger me if I'm going to manually copy each page to work on the new draft. !!!!! I'm now regretting moving our documentation to Confluence.

            Midori added a comment -

            For those who would use this feature primarily for archiving (pages, comments, attachments), Archiving Plugin gives a better (automated) solution to your problem, than copying pages manually.

            The plugin's primarily aim to detect outdated pages and notify the persons who are in charge to update it (original author, last author, space admins). If nothing happens for a period of time, then the plugin automatically moves that content to archive spaces. It preserves page hierarchies, attachments, comments, pretty much everything. The content in the archive spaces does not "pollute" search results, activity streams, essentially making the original space clean and fresh again.

            If it sounds like a compelling solution, install the plugin easily with Universal Plugin Manager, and read the user documentation to learn all features (there is a lot more!).

            Midori added a comment - For those who would use this feature primarily for archiving (pages, comments, attachments), Archiving Plugin gives a better (automated) solution to your problem, than copying pages manually . The plugin's primarily aim to detect outdated pages and notify the persons who are in charge to update it (original author, last author, space admins). If nothing happens for a period of time, then the plugin automatically moves that content to archive spaces. It preserves page hierarchies, attachments, comments, pretty much everything. The content in the archive spaces does not "pollute" search results, activity streams, essentially making the original space clean and fresh again . If it sounds like a compelling solution, install the plugin easily with Universal Plugin Manager, and read the user documentation to learn all features (there is a lot more!).

              nbhawnani Niraj Bhawnani
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              925 Vote for this issue
              Watchers:
              400 Start watching this issue

                Created:
                Updated:
                Resolved: