How do I setup my change history numbering to have floating point numbers?

[Deleted user]

I would like to show approved pages with whole numbers and unapproved pages with floating point numbers and have this increment if possible.

Eg

v#.001 .. v#.999 would show that the page has not been approved but changes have been made.

v1.000/v2.000 etc. would show pages that have been approved and released.

[Nic Brough -Adaptavist-]

I know what you're getting at when you say "floating point", but it is not quite the right phrase.  A floating point is a representation of an integer and then a part of an integer, which may even be irrational.

You are looking for a stepped (integer) numbering of releases or version system.  The most common one is x.y.z - the x is typically a massive structural re-architecting, rebuild or re-direction (or at least marketing of more of the same), the y is "no massive change but some significant new or fixed stuff" and z is "a point release fixing a handful of bugs, or adding tiny new features that don't materially affect most people"

Confluence does not have that sort of scheme for pages.  Each edit creates a new, sequential, version of the page.

There are a couple of apps that can redefine the underlying numbering scheme, but the ones I have used are not (yet) available on Cloud.  The best I can do is point you to the Comala Document apps which (if they are close to their Server versions) can create a new numbering scheme (Confluence will carry on with its simple sequence, but Comala can maintain an x.y.z format alongside it, as well as do approval and release stuff)

[Deleted user]

Thanks for the lesson in document numbering and what Confluence cannot / can do.

Unfortunately downloading suggested apps or "other solutions" is not what I am looking for.

I am sure Atlassion will have this covered in future if there is enought demand.

Cheers

[James Conway]

Hi @Nic Brough -Adaptavist- 

Thanks for the recommendation. Just to clarify that this functionality is currently only available in our Server and Data Center versions of Comala Document Management. This capability is not on our immediate roadmap for Comala Document Management Cloud. 

Community members interested in this functionality for Confluence Server and Data Center can have a look at: Use metadata to increment composite major, minor, patch content version on an approval decision requiring a parameter

Kind regards

James
Senior Product Manager