The Legacy Editor is being deprecated in Confluence Cloud: Here’s what you need to know

[Elle Ky]

@Chris 

To investigate and address your concerns, we will need more specific details and examples of what you’re seeing. Community posts are great for general discussion, but for technical issues like this, opening a support ticket is the best way for us to track, troubleshoot, and provide updates on your case.

Could you please open a support ticket and include:

• The specific page(s) you tried to convert
• Screenshots or screen recordings showing the image layout issues
• Details about your workflow and what’s not working as expected (expected vs. actual behavior)

This information will help our team understand the problem and work towards a solution. We’re committed to improving the editor experience and your input is invaluable in that process.

Thank you for your understanding and cooperation.

[Chris]

Opening a support ticket will be my next step.

I thought I was fairly clear on our issue back in Aug: https://community.atlassian.com/forums/Confluence-articles/The-Legacy-Editor-is-being-deprecated-in-Confluence-Cloud-Here-s/bc-p/3098822#M14356

I posted right after your post claiming 'will continue to roll out additional improvements over the next month' but have not heard any new udpates related to images in that time.

When you claimed additional image updates were coming, I did not press the issue. It now sounds like there are no additional image changes incoming, or I feel you would have said or hinted as much in your recent reply, so a ticket is indeed warranted.

My concern is that this new image display style is 'the new normal' and we are being sidelined as an outlier for our use and will be expected to 'make it work'.

[Chris]

I even took the original articles advice and joined the Confluence Cloud Legacy Editor Deprecation and reposted my Serious Concern with Images.

My only response was from another concerned user.

[emanuel.m.fernandes]

@Elle Ky What we've been writing all along is pretty explicit. Additionally, you are the owner of some existing issues like this CLOUD-12503 — where I've already stated that this impacts my workflow in previous comments (and others also stated the same).

We need to be able to reuse images from other pages, so that we can upload only once and use it everywhere with the additional benefit of central updating images —  to update an image we just need to re-upload again with the same name and it will update everywhere!

Can you please answer about this opened issue on your side? What additional information do you need? I've already had a session with a Atlassian representative showcasing how we use this feature on a video conference meeting. I believe you have all the information on your side — just need to act.

And will open other issues, since you are asking... To others, do the same, open issues!

[Chris]

This ticket was closed but would seemingly have been the solution to our issue:
https://jira.atlassian.com/browse/CONFCLOUD-68501

[Susanne Ertle]

I just tried the conversion of a "difficult" page with bodied macros again.

Image conversion is still not properly working and requires manually editing the Legacy content macro in the converted page, as the image sizes and positions are not retained. Even your new Legacy content macro doesn't work properly, isn't capable of showing the content as it was, so it's basically useless.

It's been more than 4 months since the announcement, where are all these constantly rolling out improvements that we were promised? 

Also, I still maintain that not having nested bodied macros in the new editor is an absolute dealbreaker, amongst others because it makes the "reusable content" argument obsolete - doesn't apply anymore, since reusable content needs to be added in other pages through bodied macros.

[Chris]

I found the original article where it mentions the Legacy editor not going away: Change to your content is in your hands ...

It would appear you forgot to include "we'll make sure to explicitly communicate well in advance that we will be moving forward 'as is, regardless of who it may affect.

[Chris]

Update, for all those following this thread.  My suggestion, do not expect ANY further changes and start designing workarounds and new processes NOW to fit THEIR 'new' editor coming in January. And, my recommendation, start redesigning your pages now to avoid all remaining uses of the 'Legacy Macro' so you do not have to go through this mess again in another year...when they decide they no longer want to support and forcibly remove that final thread.

So, our team DID open a support ticket.  Paraphrasing the reply: Sorry, not sorry that we are unable to support your issue. Nor will we address the exact ticket you brought up that may be the solution to your problem, or that you note this was mentioned as a concern over a year ago.  I see you opened this support ticket on a Thursday and have not responded in 3 days (including the weekend), so we will auto-close before you begin work on Monday (while I can comment to reopen, this felt like an extra slap in the face to our issue). And, while the support response did claim it is possible to 'meet our requirement' and provided a workaround in the support ticket, the workaround is at best a loose band-aid that will add hundreds of hours to our overall workflows to properly maintain images the way we used to.

I grade overall support of our issue 2/10 and -50/10 on handling this transition. I guess thank you for ensuring job security and potential overtime approval by artificially causing expanded workloads?

[Elle Ky]

@Martina Guth and others:

I'm excited to share that Confluence Cloud space admins now have access to a new tool for viewing legacy pages and templates. 

Space admins can now easily export a CSV list of all legacy pages and templates in their space. This makes it easier to plan for the upcoming deprecation of the legacy editor. This addresses two outstanding feature suggestions:

• https://jira.atlassian.com/browse/CONFCLOUD-77396
• https://jira.atlassian.com/browse/CONFCLOUD-78527

This is currently rolled out to 50% of customers and is expected to reach all customers by the end of this week.

For more details and instructions, please see our announcement.