Hi 00572623802f 

really nice of you to create this plugin and provide it for free, really & highly appreciated!

And still, we see this as an essential, which needs to come from Atlassian as every customer with a bit of content will have major struggles here. 

The Struggle is sitting deep, you have pages, templates, drafts, you have tons of spaces with different responsibilities and restrictions.

The node.js currently provided, is not even covering the issue entirely and is a lot of effort for the administrators.

Really an unneeded and additional workload is pushed onto the Atlassian Admins and the end-users in the organizations, without the right insight ant tooling to tackle the undertaking.

It's clear that Atlassian is aware of the complexity, look at the roadmap / deadline until this is coming. I think it just didn't click, how huge the impact will be, and how much proper tooling is missing / needed in order to handle this situation. 

I still see the need for Atlassian to deliver here properly, so open feedback is the way to go.

Thanks & BR

Sascha 

Hi 24a23f533b8a,
When you use our macro, you can list legacy editor pages per space: https://marketplace.atlassian.com/apps/1226276/keep-it-up-to-date

I know, this is maybe not the right place for my request, but it belongs to the legacy editor topic: What about the templates in legacy editor? We need as well an option to change them by clicking a button like the pages. Otherwise we need to recreate dozens of templates. Is there any plan for that?

Greetings,

Martina

The option, which would help us most, would be the opportunity to show if a page is in legacy or new editor  as a value in the content manager. This way, every space owner can directly have a look at the pages, that need to be changed. He or she can see the process and we as system admins do not need to provide lists after lists, to update how many or which pages need to be adjusted.

I completely agree with the other comments. This is now a must have with the planned Legacy Editor depreciation in 2026.

A quick node.js tool was developed after we asked to the support several times to produce such listing for our instance.
It does not replace a dashboard accessible to space administrators, but that is a great help.

Big thanks to Avhram K, from Atlassian.
https://confluence.atlassian.com/confkb/export-list-of-legacy-pages-and-their-eligibility-status-1587937727.html

We make a free addon, Keep it up to date! This addon has a macro you can insert into a page to show a table with pages using the Legacy Editor (the Keep Legacy Editor macro).

This makes it simple to look for pages which need updating due to the legacy editor deprecation.

Hope this helps!

From https://community.atlassian.com/forums/Confluence-articles/The-Legacy-Editor-is-being-deprecated-in-Confluence-Cloud-Here-s/bc-p/3057169#M14147:

Admins can use a script to export a CSV list containing the conversion eligibility of of all legacy editor pages. Instructions on how to create this list can be found here: https://confluence.atlassian.com/confkb/export-list-of-legacy-pages-and-their-eligibility-status-1587937727.html 

Following this feature request. Would be nice to locate legacy editor pages so we can prep for the migration in early 2026.

I'm surprised that this feature wasn't delivered before the announcement of the legacy editor deprecation.