nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Legacy Editor Deprecation: High-Level Feature Support Overview

Elle Ky_mfm1i3

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.
Roadmapped = This is actively being worked on, please follow the linked ticket for latest updates.

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	Supported* * 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	Supported	https://jira.atlassian.com/browse/CONFCLOUD-68780 https://jira.atlassian.com/browse/CONFCLOUD-78511
Ability to adjust font size	Supported: A new “Compact Mode” that introduces a preset smaller font size and tighter line spacing to better support information dense content Roadmapped: A new "small text" option to insert smaller text in parts of your page. Evaluating: Further customization of font size	https://jira.atlassian.com/browse/CONFCLOUD-46077
Converted page adds blank bullet items in a list	Supported: 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 Roadmapped: 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	Supported: We are fixing a bug in the conversion flow that causes multiple images in a single line to not convert properly. Will not support: This approach does not allow the creation of new content with this pattern.	https://jira.atlassian.com/browse/CONFCLOUD-69374
Additional support for new creation of native nested bodied macros	Evaluating* We are evaluating solutions to support the creation of new content with additional native nested bodied macros	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	Roadmapped: Optional line numbering Evaluating: title, starting line number Supported: Collapsible using expands 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	Roadmapped
Layout improvements	Roadmapped: resizing layouts	https://jira.atlassian.com/browse/CONFCLOUD-25519 https://jira.atlassian.com/browse/CONFCLOUD-81588
Ability to use a plain text markdown editor	Roadmapped	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	Supported: 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
Support for migrating existing nested bodied macros	Supported* We already support the conversion of pages with this type of content through the legacy content macro.
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

Comments

Ø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.

Steven Rhodes

Add attachment from another page or space is evaluating? I can't believe this feature was removed in the first place. This causes so much overhead as it is, and it costs Atlassian money in unnecessary storage as attachments are added over and over again to pages instead of being reused.

Robert Eiser

This is a helpful page, thank you.

A suggestion for addition to this list: being able to upload a new version of an attachment directly from the preview. https://jira.atlassian.com/browse/CONFCLOUD-77630

The biggest pain points for us with the conversion to the new editor:

Native support for nested body macros
Add attachments from another page or space

These are what create the most effort for users when updating a page that was laid out before the transition.

Elle Ky_mfm1i3

@Øyvind Matheson Wergeland

Regarding CONFCLOUD-78762: Page properties Report max results per page increase, I’ve passed your feedback, including the suggestion to raise the limit (for example from 30 to something much higher as an interim step), directly to the team that owns the Page Properties Report. Unfortunately, this isn’t a quick “5‑minute” change because of performance and reliability concerns, but your feedback is exactly the kind of signal they use when reviewing priorities.

I can’t promise a specific timeline yet, so please keep watching and voting on https://jira.atlassian.com/browse/CONFCLOUD-78762. Any updates from the team will be posted there. Thank you again for the clear feedback and for bearing with us while we work through these gaps!

Elle Ky_mfm1i3

@Rebekka Heilmann _viadee_

Thank you for sharing this context, I can understand how painful nested macros + unsupported macros are when you’re trying to move that many users.

Because you’re seeing a lot of issues with nested bodied macros, I’d recommend reaching out to your Atlassian Cloud Migration Manager (or if you're working with a customer, asking the customer to reach out) to discuss options for nested bodied macros remediation.

We have a dedicated team that builds solutions specifically to help with nested bodied macros and other complex content patterns for migrating customers. In many cases, it's possible that we can automate the manual page re‑design work you’re describing.

Lingaraj patil_s6ym98

Table edit view in cloud editor is not good. all columns are squeezed, and I need to adjust every time when I want to edit the table content. Please don't deprecate the old editor until you find some solution. Proper width is not set based on the column content for each column and can't read the content of column until I adjust it. Cloud has become Bizz word for Confluence but not much value added.

lk_quer1b

@Elle Ky @Howard Ng

After a page converts to Cloud automatically or manually, the page aligns left, but tables center aligns. Users must fix this manually, requiring significant effort.

Fixing these bugs before the deprecation project starts is important.

CONFCLOUD-78990: Inconsistent table alignment after converting legacy editor pages to the new editor

The auto converted pages are center-aligned

lk_quer1b

@Elle Ky please review and consider this issue -

Managing document versions in Cloud is impossible compared to the Legacy experience.

Several bugs affect this functionality. Fixing them before deprecation is crucial; otherwise, users will lose the ability to manage document versions in Cloud and and must find alternatives

CONFCLOUD-81794 Link for PDF attachment preview changed to attachment download after switching to the new editor (including previewing the latest document version) - in progress and due by Dec 24.

Uploading new attachment versions in Cloud is problematic. At least one ticket below must be fixed before legacy editor deprecation.

Add ability to update an attachment without visiting the attachment page CONFCLOUD-77630
Add search functionality on the attachments page CONFCLOUD-83324

thank you

Elvar Böðvarsson

Anything regarding how to add a reference to an existing attachment on the same page like you could very easily do way back by just starting with ! and then you would get a dropdown to select the attachment you want to add to the page?

For example, you add a pdf to the page through the attachment view or through the attachment macro. Then you can by no means add that pdf to the page so that it shows up like if you would drag and drop a pdf directly in the editor.

Barbara Szczesniak

To add an example to the response from @Elvar Böðvarsson, I would like to be able to use an image multiple times on a page without needing to insert it in the new spot, which creates a new version of the attachment even though it is exactly the same.

For example, if I create a "Learn more" button using an image that is a link, I might want to use that image 6 times on a page with different links.

Stefan Vollmer

@Elle Ky - is there any update on that list available? To watch the associated tickets is not helpful, because there are also no updates.

Espacially on [CONFCLOUD-78513] Nest Expand or other Bodied Macros in another Macro - Create and track feature requests for Atlassian products.

... which is one of the highest rated issues on CONFCLOUD. I am extremely disappointed with the very limited updates, especially regarding the tickets on the Cloud Editor that are most important to users.

Darryl Lee

Hey @Elle Ky I know we're all busy as hell but since you are making active progress on moving from Will Support to Supported some of the items you originally posted, you should know that the forums make it really hard to see those changes. I think if somebody is watching this specific post they might see the change, but otherwise somebody coming to the post new would not know what is new.

Improvements like new Max option in Adjust Width and Compact Density are great steps forward, but they're just not visible to users unless you're like @__ Jimi Wikman camped out watching App updates every day in Atlassian Admin (which normal users wouldn't even have access to).

If you and Atlassian are unable to get these changes into the Atlassian Cloud Documentation blog or in the monthly email for bundled track (which only goes to Org Admins) before (or heck after) they get pushed to sites, then sigh, I guess I'm asking you to post the feature here. As an article in the Community Forums (sic). Like so many other PMs end up doing. (Don't get me started.)

So here, I did this one for you:

🔍 What if Atlassian released a new New Compact Density Feature and didn't tell anyone?

But yeah, I don't use AI to fix my tone, so you probably don't want somebody like me writing these up and adding all my snide commentary.

I mean, you could just take the lead from Jimi and copy and paste from the App updates, similar to what he did here:

Adjust width dropdown for Confluence pages and live docs

I don't mean to diminish Jimi and his great work. But it's not quite OFFICIAL, you know what I mean?

Oh but I will point out that Jimi goes step further and includes a screenshot. Screenshots are nice. You guys should do that in your release notes/blog.

OH OH, the other thing is, if you're going to reference old JAC tickets as "Supported", it'd be nice if you dropped a update in those tickets (as @Stefan Vollmer just pointed out) so that people that have been watching those tickets for the last 7-9 years (for at least a few) can find out that they're finally being worked on!

That'd be another great way to get the word out!

Thanks!!

Nahla Mellouki

How about the macros related to Workflow like Workflow metadata, Workflow status. Workflow approver....

Welcome!

It looks like you're new here. Sign in or register to get started.