As a note: I got confused on the 'resolved' status here. This issue is not resolved, but timed out. An issue with a earlier number, but the same contents is CONFCLOUD-6373.

Would be better to have this issue marked as duplicate of 6373 instead of 'resolved'?

Hi samhasler, soft911563634, et al,

We hope you ultimately find the solution you're looking for.

In the meantime, we realize that for some users looking only for the forced comments functionality - the full engineering essentials plugin may not be necessary.

We would like to help by offering a discount in these circumstances. Please contact us referencing this issue, via any of the methods on our vendor profile:
https://marketplace.atlassian.com/vendors/1211467

Best regards,
Precision Plugins

It's really strange that this small trick (comment is required) need to be installed by some plugin.

Really guys, give us at least - "required comments" option.

The thing isn't about price, this option is too obvious and too simple for the plugin.

Also, could this have Component set to "Editor - Page / Comment Editor" and Sub-Component to "Editor - Other" please.

@Bill Arconati, Can this be reopened please? The plugin that is suggested is too expensive for such a minor feature. It would be better if it was part of the core product and shouldn't be considered a resolution for it.

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

We are going to review the two fields (comment & major/minor edit) in the upcoming versions of Confluence, but we currently do not have plans to make comments mandatory. This feature would be fairly easily implemented as a Confluence plugin.

I'd like to be able to do this on a global or per space level for exactly the same reasons as Darryl, with the space level settings over-riding the global settings. It'd also be good to be able to set it at a major/minor edit level; although this does open up the issue of what a major/minor edit is and hence whether a comment is required, I think it could be useful.