Summary

enterprise customers require an officially supported, in-product tool to export a comprehensive list of legacy editor pages along with their conversion eligibility status. The current reliance on an unsupported, "as-is" JavaScript file (`legacy-editor-export.js`) introduces significant risk and uncertainty into mandatory migration projects.

Description

As Atlassian moves towards the complete deprecation of the legacy editor, customers are tasked with the large-scale project of identifying, assessing, and converting thousands of pages. The only tool currently available to help customers scope this effort is the `legacy-editor-export.js` script.

However, the knowledge base article that provides this script explicitly states it is offered "as-is" and is "not officially supported by Atlassian." This presents a major challenge for enterprise customers for several reasons:

• Planning Risk: Basing a critical, time-sensitive migration project on an unsupported tool is a significant risk. The script could become outdated, produce inconsistent results, or fail to run in future browser versions without any official recourse.
• Lack of Reliability: Customers can't be certain that the eligibility statuses returned by the script are definitive or will align with future changes to the conversion engine.
• Administrative Burden: Requiring administrators to manually run a JavaScript file from a browser console is not a scalable or enterprise-grade solution for managing a site with thousands of pages.

Suggested features:

Implement a native, officially supported feature within the Confluence Cloud administration interface. This feature should allow a site administrator to:
1. Trigger a site-wide scan of all legacy editor pages.
2. Generate and download a CSV or report that includes key information for each page: Page ID, Page Title, Space Key, and the official `Eligibility Status` (e.g., SUPPORTED, PARTIALLY_SUPPORTED, UNKNOWN).
3. Have confidence that the tool and its output are maintained and supported by Atlassian.

Expected outcome:

By implementing this feature, administrators will be able to:

• Accurately Scope Migration Efforts: Reliably determine the exact number of pages that require manual intervention, allowing for proper resource and timeline planning.

• Reduce Project Risk: Eliminate the dependency on an unsupported tool for a business-critical process.

• Increase Administrative Efficiency: Provide a simple, UI-driven method for gathering essential data without requiring manual script execution.

• Build Trust: Demonstrate that Atlassian provides enterprise-grade administrative tools to support its customers through product transitions.