-
Suggestion
-
Resolution: Fixed
-
None
Hello Everybody,
Thank you for your patience (and humor) as we built this feature. I’m here to report that we’ve been building and testing this feature internally and it is now ready for primetime. We plan to roll this feature out in a phased manner starting next week (August 31st). You should be getting this feature on your instance in the next 2-3 weeks. Here’s a community post that explains what this feature will look like in the new editor - https://community.atlassian.com/t5/Confluence-articles/The-ability-to-add-version-comments-is-BACK-in-Confluence-Cloud/ba-p/1464221
Thank you for your interest and patience with this request. I can confirm that we are going to be introducing this feature (permanently) in the new editor. We are going to start working on this in the next few weeks. We will make sure we keep the status of this ticket updated and give you a rough ETA when we have one.
Thanks,
Sai
As we're working through this feature and others, we wanted to address a lot of your concerns as to the future of the new editor and legacy editor.
Please read our recent community post here: https://community.atlassian.com/t5/Confluence-Cloud-articles/Change-to-your-content-is-in-your-hands/ba-p/1324476
Thanks,
Avinoam
Hi everyone,
Thank you for your feedback on bringing back the "What's Changed" comment box when publishing a page in the new editor. To set the right expectations, in our public editor roadmap here https://confluence.atlassian.com/confcloud/confluence-cloud-editor-roadmap-967314556.html you can see that our focus in the short/medium term is on bringing back some of the key documentation features like linking to an undefined page, linking text to an attachment, linking images etc.
You are still able to use Page History and Compare Versions to provide more objective and reliable logs of what has been changed. We'll revisit this suggestion once we get through some of the more burning areas of feature gap feedback we've been getting for the new editor. Thank you again for your feedback.
Best,
Sunny
Suggestion
Bring back the "what's changed" comment box when publishing to the new editor.
Workaround
Two possible ways to add comments when saving changes to a page:
1) Keep on using the old editor until this feature will be implemented in the new one as well.
2) Push a change comment to Confluence using REST-API
curl -u EMAIL-ADDRESS:API-TOKEN -X PUT http://YOUR-INSTANCE.atlassian.net/wiki/rest/api/content/CONTENT_ID -d '{"type":"page","title":"NEW TITLE","version":{"message":"CHANGE COMMENT", "number": 2}, "space":{"key”:”YOURSPACEKEY”}}’ -H 'Content-type: application/json'
Note
In order for the above to work, you MUST supply a new title and the next version to be generated (thus, if you are up to version 2, change this to 3, and so on.) The Confluence title can be changed within the UI afterwards.
- is duplicated by
-
- Closed
-
- Closed
- relates to
-
- Closed
- supersedes
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[CONFCLOUD-65695] Bring back the "what's changed" comment box
<a href=" https://qaabildigital.com/ui-ux-design-service.php" rel = "Dofollow" > UI UX designer </a> is crucial to just about everything. It renders the latest technology accessible to the masses, makes our favourite apps and websites a pleasure to use, and determines which brands and products we return to over and over again. To put it simply, design matters.
Hello All,
This is Mike from the Confluence team.
You are once again able to leave a comment when publishing!
Unfortunately they closed the new suggestion ticket as a dupe and linked back to the 2006 one. 
Thank you Jira team for bringing this feature back, and I'd vote for making the comment for any page change mandatory.
Sai, I have voted for it, but that ticket was opened in 2006, which probably means it's dead in terms of priority.
Because the behavior is now different and worse than before (the comment field is hidden from view), I'd like a new ticket to address it for the Fabric editor, if this one is being closed.
Fantastic, great news!
I first posted on 18-SEP-2019 in support of bringing this feature back and started watching this ticket.
Over the past year I have read hundreds of people lending their support and sharing their frustration with Atlassian.
Almost 1 year to the day, on 14-SEP-2019 I will stop watching this ticket.
Best news of 2020! 
mary.connor, 25040376265a, there is a suggestion ticket for the ability for admins to set "Publish with comment" as mandatory. Please vote on the ticket here.
For accountability and traceability, Admins need the ability to set "Publish with comment" as default or make it required.
Seconded! The option is currently hidden under a menu. It was hard enough to get adoption in the old system, when the field was clearly visible next to the submit button. 
FYI, there are already tickets for this, for both Server and Cloud installs:
For accountability and traceability, Admins need the ability to set "Publish with comment" as default or make it required.
Please create an issue to track this! Thanks.
I'll check the box to see what's changed. And since I like these changes, I'll go ahead and leave that box check-marked as well.