Legacy Editor Deprecation: High-Level Feature Support Overview

[#1]

As we transition from the legacy editor to the cloud editor, we want to provide some clarity on which features gaps will be supported, which will not, and which are still under evaluation.

The table below is not an exhaustive list of every feature, suggestion, or bug. Instead, it highlights the major themes and some of the most impactful gaps that are most relevant for customers transitioning from the legacy editor. 

We continually re-evaluate and re-prioritize feature requests based on customer feedback and evolving needs. For features that are important to your workflows but are not covered in this table, please search for them under Confluence Cloud suggestions on jira.atlassian.com. Voting and commenting on suggestions helps us prioritize improvements that matter most to you.

💡Tip: To track progress and receive ongoing updates, please "vote" for or “watch” the associated tickets.

Understanding “Support status”:

• Supported = This is now supported; a solution has been delivered to address this.

• Will support = We are planning to deliver a near-term solution before the deprecation of the legacy editor.

• Evaluating = We plan to actively investigate these suggestions and explore possible solutions over the next quarter. While support isn’t guaranteed, we’re considering all options. If prioritized, solutions may be delivered after the legacy editor is deprecated.

• Will not support = We do not have near-term plans to address this in the next two quarters.

Note: This table is not an exhaustive list of every feature, suggestion, or bug we're working on. 

Feature	Support status	Associated ticket
Unblock unsupported pages for conversion to cloud editor	Will support* * We are continuing to address unsupported use cases to ensure that, by the time deprecation begins in January, nearly all content will be eligible for conversion. For the small number of pages that remain unsupported, please note that these pages will still be viewable even after the legacy editor is deprecated.
Increase maximum width of pages to better support content on wide screen monitors	Will support	https://jira.atlassian.com/browse/CONFCLOUD-68780 https://jira.atlassian.com/browse/CONFCLOUD-78511
Ability to adjust font size	Will support: A new “Compact Mode” that introduces a preset smaller font size and tighter line spacing to better support information dense content Evaluating: Further customization of font size	https://jira.atlassian.com/browse/CONFCLOUD-46077
Converted page adds blank bullet items in a list	Will support: For converted page, we will wrap this in a legacy content macro to support legacy pages to be converted to the cloud editor. This approach means that newly created pages won’t be able to use the same pattern Evaluating: Native support in cloud editor so that newly created pages can use this pattern	https://jira.atlassian.com/browse/CONFCLOUD-79557
Image conversion: multiple images in a single line appear on separate lines after conversion	Will support: We are fixing a bug in the conversion flow that causes multiple images in a single line to not convert properly. This approach does not allow the creation of new content with this pattern.	https://jira.atlassian.com/browse/CONFCLOUD-69374
Native support for nested bodied macros	Evaluating* * We already support the conversion of pages with this type of content through the legacy content macro. However, this approach does not allow the creation of new content with these patterns so we are evaluating solutions to address that need.	https://jira.atlassian.com/browse/CONFCLOUD-78513
Custom font color and additional color options across editor elements (status, panels, etc.)	Evaluating	https://jira.atlassian.com/browse/CONFCLOUD-67183
Code block improvements	Evaluating: Collapsible, title, line numbers Will not support: Theming	https://jira.atlassian.com/browse/CONFCLOUD-67816
Provide a report with all pages using the LCM macro	Evaluating	https://jira.atlassian.com/browse/CONFCLOUD-83006
6-level indentation limit for lists	Evaluating	https://jira.atlassian.com/browse/CONFCLOUD-81750
Table improvements	Evaluating
Layout improvements	Evaluating
Ability to use a plain text markdown editor	Evaluating	https://jira.atlassian.com/browse/JRACLOUD-72631
Add attachment from another page or space	Evaluating	https://jira.atlassian.com/browse/CLOUD-12503
Panel improvements	Supported: Users can click on a converted panel macro and “edit” to open the configuration panel and edit the title Will not support: Bringing back the visual aesthetic of the legacy panel macro. We encourage users to use the new panel macros, or use tables or layouts to achieve their desired visual styling. The ability to nest panels will be explored as part of “Native support for nested bodied macros.”	https://jira.atlassian.com/browse/CONFCLOUD-75113
Space admin tool improvements	Will support: bug fixes to address timeout errors Will not support: site-level report	https://jira.atlassian.com/browse/CONFCLOUD-83179
Shipped – Now Supported (not an exhaustive list)
Admin tool to export a list of legacy pages with eligibility status	Supported* (announcement) * We are aware of a bug impacting the experience and are actively working on fixes. Please follow CONFCLOUD-83179 and the community post for further updates.	https://jira.atlassian.com/browse/CONFCLOUD-77396 https://jira.atlassian.com/browse/CONFCLOUD-78527
Attachments should show as a card after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-82325
Images: Ability to change image alignment within tables, panels, and expands	Supported	https://jira.atlassian.com/browse/CONFCLOUD-68427
Images: Fit images to window for images without width attribute	Supported	https://jira.atlassian.com/browse/CONFCLOUD-82240
Images: Retain fixed width behavior of images during editor conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-82061
Images: Images should retain alignment after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-76580
Images: Inline images need to be editable after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-77304
Images: Ability to edit, resize, and adjust alignment of images after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-65597
After converting a panel macro, user should be able to edit the title	Supported: Users can click on a panel macro and “edit” to open the configuration panel and edit the title Will not support: Bringing back the visual aesthetic of the legacy panel macro. We encourage users to use the new panels or use tables to achieve their desired visual styling. The ability to nest panels will be explored as part of “Native support for nested bodied macros.”	https://jira.atlassian.com/browse/CONFCLOUD-75113
Table headers are misaligned after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-79469
Table header rows or columns get un-bolded	Supported	https://jira.atlassian.com/browse/CONFCLOUD-77503
Status macro on legacy editor changes text to DEFAULT after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-77503
Extraneous lines are added between content after conversion	Supported	https://jira.atlassian.com/browse/CONFCLOUD-76553 https://jira.atlassian.com/browse/CONFCLOUD-81735 https://jira.atlassian.com/browse/CONFCLOUD-76554
"Optional Titles" from Info/Note/etc. macros should be converted to bolded normal text, not converted to H3	Supported

[Øyvind Matheson Wergeland]

@Elle Ky thank you for sharing this list.

Please consider adding extending the max number of pages in the page properties report: https://jira.atlassian.com/browse/CONFCLOUD-78762

At least just extend the max limit from 30 to e.g. 300 - this should be a 5 minutes fix. Then you can go back and revisit the sorting issues later.

This is the single feature that blocks us from converting all of our pages (although not being able to fix table columns is quite bad for us as well).

[Rebekka Heilmann _viadee_]

Thank you for the Update!

I am currently migrating ~10.000 users from DC to Cloud and see the most issues with nesting macro capabilities. People have to completely redesign their pages for them to properly work in the new editor, even with the Legacy Macro. Pair that with unsupported macros and the perfect storm is created. 

It's very helpful to get an idea of what's going to be (un-)supported though to prep documentation and training for it.