Hello,
we work on three versions of an application at once. We document these versions on one page that we would like to version (either as separate pages or the same page). In V1 page, the oldest version, we may change a picture and we need to see the picture in V3 also. But this updating is quite hard to accomplish.
I have already tried Scroll Versions - when we edit the V3 page and then in V1 page we add a picture, it is not automatically inherited into V3 page, as V3 was changed from V1. Merging would rewrite all the new content in V3.
I have also tried Page Branching for Confluence, which allows me to update a branch (branching from a page), but does not allow for multiple branches (a branch of a branch). The use case here would be sort of an infinite branching as versioning...
It would be best if we could choose the parts to merge.
Do you know of such an add-on or a methodology to allow for this type of version control and updating?
Hi @Kamil Beer
do I understand correctly that you would like the content in v3 to be the new one, while an image should always be inherited from v1?
If all the content should be inherited again from v1, then you could remove the changes in v3 with Scroll Versions so that the page starts inheriting again.
Cheers,
Roman.
@Kamil Beer - Did you ever find an answer to this question? I have the same use case and have not found a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.