This will be very helpful for my organisation to keep a good documentation tracking. 

Yes.

We need that feature in out organisation

I support this idea, it is very important

Hello everyone! If anyone reads this, this request is deemed NOT BEING CONSIDERED. 

 Please go to this request: https://jira.atlassian.com/browse/CONFCLOUD-67035

Which is gather interest. Thank you! 

I am totally agree and in our company we would love to have also this feature. This should be configurable.

This is a really important feature to have a proper traceability of the changes. Without forcing the user to write a comment, the Version History macro is completely useless.

This would also be useful for our organization. 

This would be a useful feature for our organization. It is too easy to forget to write the comment and it cannot be edited afterwards.

Please reconsider this feature, Users has habit to "forget" this text field. 

We need this feature to ensure ISO 9001 compliance and really want to have it. With the discontinuation of hosted, we also no longer have any option to engineer and alternative.

This is a feature that will be beneficial to our organization as well.

Yes, this should definitely be something we could choose to turn on and off for each space.

http://4gamesonline.com
http://cheatjudionline.com
http://cariagenjudi.com
http://sebarkanberita.net
http://scoreparlay.com
http://kickoffbola.com
http://gulasusu.com
http://renyaheuy.com
http://susumerah.com

We would love to run the cloud version but little things like this keep us hosting our own.

 I agree. Such comments vastly increase the transparency of changes and make it easier to fix wrong changes.

People like to forget about this field, so making it mandatory would force them to use it.

This would be really helpful! In a VCS (git/svn/etc.) you also have to write a commit message.

This would help us a lot. Please reconsider.

Hi all,

Thanks for your interest in this issue.

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

This suggestion will be reviewed in about 12 month's time, at which point we’ll consider whether we need to alter its status.

Best,
Confluence Product Management

This is only fixed in the server version through the plugin  Engineering Essentials but I would like a fix in the cloud version

@cesar i said it SHOULD be configurable

Dana Jansen where is that configuration?

This should be configurable at the general configuration level AND space configuration level.

I would also really appreciate this feature because of the many versions of the files we expect.

We have some pages handling documentation for projects in relation with FDA and customers there version control and change history for documentation is mandatory. We have set up a procedure for documentation handling using Microsoft Word and Confluence but it would be a lot more elegant and much more simple to have the Confluence pages handling everything. The only piece we are missing is to able to enable mandatory version commenting for those pages.
We would have a look at Engineering Essentials but I still think this should be a configurable option in Confluence for each page.

We are using our own server installation.

This is needed for us (using cloud instance) too...

is there an update on this request?

It's so nice to have feature request created on '16/Jun/2006 1:01 PM' and still not resolved.
Could you please finally handle it?

This "Engineering Essentials" doesn't work for our company, because we use a Cloud instance. Also, I agree with Dana's comment from July 2014, that this should be configurable item on per-space basis.

Engineering Essentials has just been released to the public. https://marketplace.atlassian.com/plugins/com.precisionplugins.engineeringessentials

This enables each space to be configured so that version comments are necessary.

With Engineering Essentials it is now possible to configure an entire space to force version comments. Any enabled space will require a comment before saving a page. Via the button and the shortcut key. Users can still edit pages without fear of loosing work as the draft backup process is maintained. No additional editing of a page is required. This enforces a consistent look and feel within each space.

As forcing version comments is often required for formal documentation we've also provided the ability to separately enable numbered headings for all pages within a space. This resolves the issue of numbered headings space-wide, without needing to put your content inside a macro, among other benefits.

With years of experience supporting Confluence in an engineering environment, Precision Plugins have big plans to plug some small gaps, helping Confluence and other extensions be the best environment for your formal documentation.

Checkout the Engineering Essentials package and let us know what you think here:
https://marketplace.atlassian.com/plugins/com.precisionplugins.engineeringessentials

i think this should be a configurable item in spaces.

Why is something like this being overlooked by Atlassian?

I think that having this as an space - or even page - option would be very interesting, and as Atlassian guys have admitted in the other issues linked above, this is fairly issue. We cannot afford being searching for more and more plugins, which may become obsolete, abandoned or simply too expensive in the future.

Please, add this to the basic functionality included in confluence.

This one would help us a lot.

We are planning to use confluence to create documents for regulatory affairs. This feature is quite relevant for us to have a clear tracking of the changes, and the fda g people would also love to see the history.
So, please just do it =)

This would be a very useful feature.

Note that this business rule would be required per page (rule would not necessarily be required for all pages).

This type of feature is often available with a version control system.

E.g. editing a Word document stored in SVN (or whatever)

As confluence has now (mostly) replaced our usage of Word documents - it would be a cool feature to be able to assert check in comments (as required)

I also strongly agree with this. I just ran into the same issue with recently with our work flow. At the very least having a option to set it as mandatory or not would be appreciated, similar to the suggestion in (CONF-15897).

I also agree with the suggested new feature. Having the option to require users to either add a comment or indicate that the change is minor would make the versioning functionality of Confluence more usable.

I strongly agree.

Very important also for our organization.

This feature would be very beneficial to our organization. We are currently using Confluence to store and maintain internal documents which we need to have control over the changes not only with who made the changes, but also the description of the changes. Adding this feature into a future release would be greatly appreciated.