Change History Overload

[Nada Elsayed]

Change History Overload: Each page lists all versions in change history, causing clutter and poor usability compared to the previous version

[Nada Elsayed]

how to use live pages

[Laura Campbell]

@Nada Elsayed You can either select Live doc when you create a new page

or you can convert existing pages to live docs through the action menu of the page (you can convert back to a regular page later if you need to)

[Nada Elsayed]

after converting to live document how to get back to the normal one

[Laura Campbell]

@Nada Elsayed You can go through the same action menu again to convert a live doc back to a page.

However if your problem was that there were too many versions being saved, you may want to keep the page a live doc so that Confluence groups edits together in fewer versions. Users will be able to view the page (and make changes) with a live doc, and you don't have to convert it back to a regular page.

[marc -Collabello--Phase Locked-]

Just FYI: Live docs are NOT suited for controlled documents, e.g. ISO procedures or similar, as versions are determined by the Confluence saving algorithm.  With a controlled document, you'd want that a specific author "publishes" a defined version.

[Laura Campbell]

Hi @Nada Elsayed 

As @marc -Collabello--Phase Locked- described, this looks like the standard Confluence behavior.

You can delete some of the versions if the changes are minor and you only want to keep the major versions.

You could also use Live pages. These detect when people start editing the page, and only create a new version 10-15 minutes after the end of the editing session. If you previously had lots of people working on a page and all publishing their changes 1-2 minutes apart, working with a Live page would group all those changes into just one version.

[Nada Elsayed]

[marc -Collabello--Phase Locked-]

Hi,

Can you maybe add a screenshot so that we can understand what your exact issue is?

[Nada Elsayed]

[Nada Elsayed]

[marc -Collabello--Phase Locked-]

These screenshots seem to display the standard Confluence behavior to list all versions.

Some users accumulate multiple edits in a draft version of a page (by not publishing after each single edit).  Then when a new page version is ready, the page is published.  This leads to less versions, and might be applicable to your use case.