-
Suggestion
-
Resolution: Fixed
-
None
-
19
-
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
- incorporates
-
CONFSERVER-28729 Insert Link to Create Page from Template
- Closed
- is blocked by
-
CONFSERVER-24678 Copying a page to a different space results in no attachments coming with that page
-
- Closed
-
- is duplicated by
-
CONFSERVER-5970 Copy page including attachments
- Closed
-
CONFSERVER-7391 copy a a pge and allsub-pages
- Closed
-
CONFSERVER-19143 Able to inherit permisison from parent to child pages
- Closed
-
CONFSERVER-30003 Copy attachments when copying and moving a page
- Closed
- is related to
-
CONFSERVER-2931 Copy page
- Closed
-
CONFSERVER-3191 Easily create a copy of an entire space
- Closed
-
CONFSERVER-28148 Confluence Dashboard page
- Closed
-
CONFSERVER-30934 Add ability to disable Space Blueprints as a site admin
- Closed
-
CONFSERVER-2085 Ability to rename space key
- Under Consideration
- relates to
-
CONFSERVER-8273 Copying a page to a new space should not prepend 'Copy Of' to the copied page
-
- Closed
-
-
CONFCLOUD-2814 Copy page hierarchy (including attachments)
- Closed
-
CONFSERVER-4010 Make news posts simply labelled pages and allow all pages to be accessed by date
- Closed
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
When we ask to upgrade to v.6.0 the response that we get indicates that Atlassian is holding themselves to a very low standard when it comes to quality assurance for a major release.:
"Since Confluence 6.0 was just released few days ago, Premier Support does not recommend upgrading to that version yet.
We want to make sure that the new release has ample time to "soak" in the wild, to minimize the chances of running into undiscovered critical bugs after upgrading. While our developers make every effort to roll out new bug-fix releases quickly to remedy critical bugs, enterprise environments often do not have the ability to quickly upgrade.
This is why we generally will not recommend the bleeding edge versions in favor of less surprises and Confluence stability. Furthermore, Premier Support will not be recommending Confluence 6.0 until the release has undergone a thorough Premier Support review with the Server development team of at least 90 days to insure that all blocking issues are corrected before the product will be recommended to our Premier Clients. This has been agreed to with the server development team to insure that our clients are provided with a stable, enterprise-hardened release.
Until such time though, our current recommendation stands at the Confluence 5.10.8 release for now. Of course, you can still test Confluence 6.0 in a dev environment, but it's definitely not recommended for the production environment yet."