Is it possible to restrict page versioning?

[Caroline Busse]

Hi,

my problem with the versioning in Confluence is, that every time I change even minor things like a missing dot on my page or don't even change anything at all but just press save, a new version is created. So that I have way too many versions in the end.

Is it possible to restrict this? My ideas are:

- only create a new version if something is really changed or

- as I work with Comala Workflows, is there a possibility to edit the version via my workflow?  E.g. if I approve my document in the last workflow state, is there a feature that allows the approver to select it's version?

Thanks. :)

[Nic Brough -Adaptavist-]

The problem here is the definition of "something is really changed".  When authoring things, a missing dot might actually fundamentally change the way content reads, so it is "something is really changed", no matter how minor you might think it is.  (I've worked with Confluence in a legal firm - they were delighted that it would consider a minor punctuation change a full "version")

So, confluence does the right thing and versions everything in full.

But it does not have a good numbering system for these versions.  Scroll Versions and Comala workflows are both good ways to improve the system, such that minor revisions are still versioned but only main versions are released / authorised / published.

[Caroline Busse]

Thanks!

But is it possible to manually type in the version numbers via workflow?

[Nic Brough -Adaptavist-]

No, the versions remain the full sequential versions.  Comala allows you to only "publish" certain versions.  Scroll Versions layers a version scheme over the top, so you can say "use Confluence version 2 for Doc version 1, Confluence 45 for Doc 1.1, Confluence 68 for Doc 1.2, Confluence 97 for Doc 2.0" and so on.  I'd guess that's closest to what you're looking for

[Caroline Busse]

Ok thanks :)