|
This is marked fixed, but is there a way to copy a page and it's children to another space?
You're right... only one part of this issue has actually been resolved. I'll re-open it.
The ability to copy spaces in their entirety would be a huge plus for our organization. We maintain our documentation in Confluence, so copying the docs as a starting place would save us a lot of time. We'll be managing projects in Confluence so being able to copy spaces as a starting point from one project to the next would be a huge asset.
Our company also really needs "copy space" functionality. We were surprised that the feature doesn't exist already, as it seems a common task.
I am now looking into using the "import page" functionality to accomplish this. Currently the easiest way to copy a space is probably to make a backup of a space, manually change the space-key in the export xml file and import the space again into Confluence.
However, you should always be careful when manually editing the xml export since there is always the possibility of corrupting data when doing so. Ability to copy muliple pages between spaces (vs. move) is a critical feature for our planned use of the tool. We don't think the WEBDAV plugin is an adaquate long term solution.
Lack of better page Copy functionality is really limiting what we can do with Confluence. For example, we would like to use Confluence for capturing and reusing testcases using the new testplan and metadata plugins. What we'd like to do is create a QA space with a large collection of testcases. Then we would copy these testcases from this archive to one or more project pages, which we already have in Confluence (Note we may have multiple projects pages in a given space). Problem is there is no way to Bulk Copy or Copy with children and attachments. Ideally, we could simply go to the QA space, check off the testcase pages we want to copy and then copy them to a target space/page with attachments. Ideally, we would also have an option to prepend a name (think project name) to each page (think testcase page) title to work around the lack of namespaces in Confluence.
Move page with children doesn't suffice because these testcases may need to be reused in multiple projects. I'd like to add another request for a 'copy space' feature in Confluence. I regularly need to create copies of spaces, which should take me thirty seconds but in fact takes me several hours.
I worked around this using the idea from Jens to export the space to XML and manually edit the space keys. I was able to copy a space that contained around 500 pages in just a few minutes. Of course I'd strongly recommend doing a backup just prior to importing just in case Extending this idea of regularly copying a space would be to "create once - export to selected spaces", that is I create a page, possibly with children and attachments, save the page and checks the checkbox "Export to..." which allows me export the complete page to several spaces at the right place in the hierarchy.
Thus I could have several partners with their own spaces to which I can push generic information. This issue is very important to me. I just lost a whole week by working around the lack of this feature.
This is a huge feature for us. We are using confluence to store spec documents for our client projects. Spec documents are initially created from a series of templates that we have created. The templates are all filled out with the information and then the spec is finalized for that project. We may modify the spec while the project is in progress to adapt to changes and new information. At the end of that project, the spec that is in confluence serves as the documentation we need to let us know all of the decisions we made for the project. But, what happens is that we repeat the same basic project for that client again next year. We don't want to modify the existing spec from the previous year because it is our only records of how everything was setup last year. But the specs for this year are going to be 75% similar to the specs for last year. Our project managers don't want to have to retype all of that information all over again, they simply want to copy last years specs and then start modifying them to meet the requirements of this years project. These specs often involve several layers of child pages with attachments at each layer. I can't make separate spaces for each project because we have many templates attached to the space and we have 100+ projects a year.
I feel confluence could be a great place to house all of these spec documents and allow teams to collaborate and communcate better about what is going on in each project, BUT I can't implement this without incurring alot of effort to copy pages. I really need the existing copy feature to copy child pages and attachments. Copying page families including attachments is an absolute need to have for us. We would like to have a separate spaces for major reworks of existing page families. To start this rework we need the possibility to copy it.
Creating a new space with permissions of an existing one would be a really helpful and time-saving feature!
Renaming and redescribing this issue to reflect why it was reopened and what the majority of the comments are saying. Having one issue for multiple ideas just confuses things.
I know you guys hate this question .... but what is the likely hood of you guys building this soon (now that it is more focused)?
What we really need is the ability to copy an entire space.I thought that is what I was voting for; however I notice that there is CONF-3191 for that; which doesn't have as many votes. I am using the workaround currently. I suppose if this one goes in first I could copy the page family and move it to a another space.
Would this issue be addressed sooner if I removed my vote from this item and placed it ONLY on CONF-3191? Maureen,
I'd like to copy from Space to Space and copy as well as copy a hirecary I don't always want to copy an entire space to a new space, although that John B. Allen "Maureen (JIRA)" <jira@atlassian.com> To: John B Allen/AMER/TRS/AEXP@AMEX [ http://jira.atlassian.com/browse/CONF-2814?page=comments#action_63634 Maureen commented on CONF-2814: What we really need is the ability to copy an entire space.I thought that Would this issue be addressed sooner if I removed my vote from this item you could instead create a copy in a different space. – American Express made the following "This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." American Express a ajouté le commentaire suivant le 08/31/06, 11:50:01 Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent renfermer des renseignements confidentiels et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Merci. Definitely agree. There has to be an easy and transparent way to:
Kind regards, There is now an FAQ available which covers two workarounds:
http://confluence.atlassian.com/x/apYC  There are two distinct feature requests open relating to copying space content.
Please be sure to vote towards the issue/s that most closely matches your needs. David Soul I'd like this feature, too. This is just one of a broader set of features that Confluence is missing around content refactoring.
Users seeking this feature as a document staging space may wish to implement the following workaround:
Have one public and one staging space. The public space has editing restricted to approved users only and a note that to edit any content in this space, please use the staging space. The staging space is a restricted to users who can contribute only. Updates are made to the staging space, reviewed and copied into the public space once approved. Cheers, I'd like this feature added, too.
My use case matches Kevin James exactly. Being able to clone a page hiearchy to the same space or a different space, with the same name or a different name, plus optionally all attachments, comments, etc. would be ideal.
Thanks. Another vote here - several, if I can represent my group.
Our use case also matches Kevin James' as well. We need to be able to move a hierarchy around in the same or a different space, and we need to be able to rename and edit all the data in it to reflect specific test cycles. We work with multiple page document templates. When we produce a new document from a template, we need to manually copy each page. Computers are supposed to make your life easier, not harder. Manually copying 20 pages each time I want to start a new document is not very efficient. Can you please implement this ASAP.
I have added an issue "CONF-11320 ability to archive comments - Atlassian JIRA" but i guess this issue fix can copy the comments would address CONF-11320 .
I wanted to add my vote for this feature. We are using Confluence for some large data calls and have set up an extensive page hiearchy to accomdate it (~100 pages). We will be re-doing this data call and other similar ones on a fairly frequent basis. It would be extremely useful if you could copy a page and all its children both within the same space to other spaces. Copy of could be added to the page titles.
Re-creating those pages over and over again is frustrating and time-consuming. /vote +1 - definitely a useful feature and its omission is confusing to users who are familiar with "move with children".
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New Feature
Open
Major
Copy page hierarchy
It should be possible to make a copy to both the current space (under new name) and another space (under either existing or new name).
From my post on the list (just a random idea that let David to point me here):
When editing a page, there is an option to "move" to another space - it would be useful if there was also a tick box (or something else?) that specified "copy" - eg. you could simply rename the page and tick "copy" to create a copy (under the new name) of that page in the same space. Or move the page to another space with "copy" set = copy page to other space. Rename + move + copy = copy to another space under a new name...
Also, please link this issue to
CONF-2931