Ability to preserve page hierarchy when publishing to existing space on a remote instance
Description
Environment
Activity

François-Jean NOAILLY March 26, 2019 at 12:49 PM
Hi,
i'm really disappointed with this issue.
We produce documentation in a collaborative mode with Confluence (private server). And our publication is on another server (public).
So it's very hard to move pages in the target space at the publication time. The "publication team" is different than the writers. They have no ideas of the situation.
Thanks
François-Jean

Nils Bier (K15t) May 8, 2017 at 9:18 AM
Hi Maria,
No, multi-excerpt will not be available with this new version (this is tracked here: https://k15t.jira.com/browse/VSN-3052).
Currently we're not able to communicate a ETA for the reuse feature, as we're still early in the process.
Please watch the corresponding issue here: https://k15t.jira.com/browse/VSN-766
As soon as there are any news, we'll update the issue.
If you have any more questions, please feel free to get in touch with us via support@k15t.com.
Cheers,
Nils

Maria Asnes May 1, 2017 at 12:52 PM
So basically you will have the same functionality for includeplus macro as Multiexcerpt?
When is this new version expected?

Nils Bier (K15t) May 1, 2017 at 12:13 PM
Hi Maria,
initially we'll start with adding the possibility to re-use content from other spaces in a versioned space (which is currently a limitation of the Scroll Includeplus macro, as it only allows you to reuse content from within the same space).
With the new version we plan to make it possible to link specific spaces (they can also be versioned if needed) and allow authors to reuse content over those (versioned) spaces.
Cheers,
Nils

Maria Asnes May 1, 2017 at 11:56 AM
Thank you, Nils
I regret to hear that we need to wait for so long.
We're also interested in content reuse. Could you please share what improvements are you working on?
Thanks
Details
Details
Assignee
Reporter

As a user of Scroll Versions I would like to have the ability to preserve page hierarchy from the source space when publishing to existing remote space.
Workaround:
Move pages in the target space on a remote system manually.