-
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.
This functionality is essential to document version tracking.
I have been pushing people in may company to add comment on what has changed in articles before publishing them so we have a better tracking of changes.
Why/how could someone decide to remove this functionality in the new version?
Sai, thank you for the update! I am very happy to hear how close this is to rollout!
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 Confluence 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
@Darren 
The hotel party idea is great
As someone mentioned above, there is no way Atlassian don't have comments on internally, there would be a riot.
Sorry for my unsubscribe email reply guys. I just found the "Stop watching" command. I had been looking for the watch "eye" icon earlier so I didn't find it earlier.
I wondered why so few watch this thread compared to those who voted for it... its presumably as all they see is chatter about why confluence has done nothing since June so stop watching.... like I'm about to.
Dammit, now I have Edwin Starr as an earworm:
"Jira feedback forms, huh, yeah
What are they good for
Absolutely nothing
Say it again..."
I like Darren's idea- we can all wear masks that have one of the following designs:
- Atlassian logo next to the phrase CONFCLOUD-6595
- A picture of the What's Changed box with the words: "What did you change?" NOTHING"
I'm going to book us all a hotel. I was thinking it would be nice to have some sort of "CONFCLOUD-65695 10 Year Reunion Party" where we can get together and reminisce about the old times, when we were naive enough to think that paying for a service gave us any sort of say in how it might work, or even have our views listened to by the people who were happy to take our money and do - well, I'm not really sure...
Hi Sai,
It's been six weeks since your last update. When can we expect an update on getting this feature parity in the new editor?
Is this still due in 2020? So many basic features of an editor have been deprecated in the new version, but somehow I bet that the amount we pay for it has not been similarly deprecated. The way that Atlassian treats paying customers is just astonishing - it's a constant process of pulling the rug from under our feet.
Hope this will be completed soon - I just a bunch of time trying to find where the comment box was when updating a page just to find it's not there
@sai - seriously? You have all these people who want to use this feature and now there is less of it than before? Please explain.
Also, can you give us an update of where things are since your status update of June 20? And is there any possibility this issue could move out of "gathering information?" Surely by now you have gathered enough information to fill the Oxford English Dictionary!
@sai: we do not use the new editor (because it's a regression) but we discovered today the "Feed" page do not report the "what did you change" information anymore. We use this a lot to know what others did quickly rather than asking them or viewing the page history or even opening the page and comparing the current version with the previous version (this is waste of time). We need this back asap.
@sai: Thank you for the update. We will all be much happier then this feature is restored, and your life will probably be calmer as well!
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.
So, let's no bother ASKING anyone if they WANT it "better", let's just slow the restoration process to allow the keyboard monkeys who screwed up the editor in the first place, make additional bad decisions...
Atlassian is crumbling under the weight of success. I have sen this before so many times. Remember Hayes modems? Remember Digital Research? Remember MCI? Remember Lotus? Should I go on?
@Kim Hirschman: I commented on the most recent "What's New in Confluence Cloud" post asking about this request (https://community.atlassian.com/t5/Confluence-Cloud-articles/What-s-New-in-Confluence-Cloud-June-2020-Edition). I got a response fro Tracy at Atlassian that said, "We have heard the feedback and understand how important that capability is. Rather than just duplicating how we did it before, we are working to make it better. The details are firming up, and we'll update you as ASAP."
Here's hoping!
I just went to the Confluence Cloud Editor Roadmap (https://support.atlassian.com/confluence-cloud/docs/confluence-cloud-editor-roadmap/) and it looks as if the "What did you change?" comment box has moved from "Gathering Interest" to "Short Term."
I don't know when this change was made, or even whether "Short Term" means that its restoration is imminent or it will reappear for a short period of time and then go away again. If the former, why wouldn't Atlassian let us know? Oh well - fingers crossed... 
That this critical functionality is still "gathering interest" makes me suspect one of these explanations:
- Adding the feature would be significantly difficult/expensive
- Adding the feature would wreck someone's ideal for their new UI layout
- Adding the feature would undermine a decision to force those with technical requirements to migrate from Cloud
- Adding the feature serves a customer demographic (technical publications) that Atlassian no longer targets
I would feel better if I could believe the first explanation, but it seems trivial: exposing one existing text field. The other options leave me cold.
I am a big fan of Confluence, but without this feature I can no longer say honestly that this is the best tool to use for writing specifications. Usually when a change was made on a feature I just wrote in the change request the link to the Jira feature. If someone needs to know why the specification has changed, this link provided everything he needed to know.
Please bring this feature back !!!
i struggle to understand why this is nearly 18months old and still not prioritised. I used to use the old version and had foolishly assumed it was still there - not going down well when i demo confluence to people.
Please restore this function. Quite surprised that this is removed. One of the really useful functions in Confluence allowing people to specify in a nutshell what changed.
How can you in your right state of mind remove such an important documentation control function? To tease, you even leave the "Comment" column in the page history. This change basically made my management ask me to look into Confluence alternatives ASAP once they realised this was gone in the new layout (yesterday). They are even considering moving our docs back into Word!! (as if that would solve the issue ).
It took me more than one year to convince them to use Confluence for documentation management, this is making all that effort go to waste.
It's hard to believe this feature has been removed. What's next? You going to remove the change history entirely?
Seriously folks, next time you get the urge to "redevelop" your user interface, you might want to spare a thought for your customers.
We have people in our organisation who still today refuse to work on content in Confluence since the removal of wiki markup editing - the WYSIWYG editor is just too much work for serious content editing.
Please restore this feature.
Still waiting for this feature to be added to the new editor. Seems crazy (and really bad UX) to show the change comments in the page history, and yet you can no longer add them!!
(Even the ability to add a comment in the page history where there isn't one would be better than the current state.)
8e30e3f3bc6d You can keep on using the old editor (TinyMCE) without needing to clone a page created with it. For details please see:
- https://support.atlassian.com/confluence-cloud/docs/learn-about-confluence-cloud-editing-improvements/
- https://community.atlassian.com/t5/Confluence-Cloud-articles/Change-to-your-content-is-in-your-hands/ba-p/1324476
Specifically:
The legacy editor template can be enabled for your site at any time.
Most sites currently have the legacy editor template enabled. If your site falls within the small percentage of sites that do not, please reach out to Support for more information about enabling the legacy template.
Yep- we're still cloning a page from the old editor whenever we need to start a new page. The DNA of that one page will be perpetuated forever...
Hey Confluence people, how's it going with this ticket? It's been open for more than a year now, would be nice to get some further update!
We need this feature and if possible to have it mandatory before a change is committed.
They have offices globally. Just go to the nearest on the same day. Agree...will need to be after lockdown!
Not to mention the difficulties in getting where their offices are...
They neither listen, nor ask for guidance on major changes that disrupt the way we work. Let's ee, a coupla thousand people standing 6' apart, we could take over the town...
Clearly Confluence are not listening. If they were then maybe they would comment in this thread.
Only way forward is to stage a rally on this topic outside their offices. Think we have enough people now to do so.
Who is with me?
Given that more and more people are clamoring for the return of this feature, I don't know how much more interest Atlassian needs to gather (see status above.) PLEASE let's get this scheduled!
Hi Confluence team,
Having this feature was a crucial factor for us to choose confluence as it's mandatory for our company from a compliance perspective.
Please bring it back.
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.