So I discovered the limitations of Rovo to help in these matters and the advantages of the support agent...
response that was actually useful:
It can be difficult to distinguish between them because they often look identical in the editor, but you can identify deprecated gadgets by checking your site's macro usage or inspecting the page's storage format.
## Identifying Deprecated Gadgets
Since there is no visual indicator in the UI to separate legacy gadgets from new macros, you can use these administrative methods to find them:
### 1. Macro Usage Report
As a Site Administrator, you can see a count of where specific macros are used across your instance .
* Navigate to **Confluence Administration** (gear icon) > **General Configuration**.
* Select **Macro Usage** from the sidebar.
* Search for the legacy gadget key, typically `com.atlassian.confluence.plugins.gadgets.gadget.lab` [^02^].
* This will provide a list of pages currently using that specific legacy framework.
### 2. Legacy Content Reporting (New Feature)
Space admins can now export a report specifically for legacy content [^03^].
* Go to **Space settings** > **General** > **Legacy content**.
* You can view and export a CSV list of all pages still using the legacy editor or containing legacy macros [^03^].
* The report includes "eligibility for conversion" and flags legacy macros that may not function correctly in the new editor [^03^].
### 3. Storage Format Inspection
If you are comfortable with technical tools, you can use the **Confluence Source Editor** (a free Marketplace app) or the **REST API** to look at the underlying code of a page .
* **Legacy Gadget:** Will appear in the storage format as `<ac:structured-macro ac:name="gadget">` .
* **Modern Jira Macro:** Will appear as `<ac:structured-macro ac:name="jira">` or use the newer `Jira Work Items` schema .
## Why They Look the Same
Legacy gadgets often remain visible in the macro browser to prevent data loss on migrated pages, but they lack the performance and security benefits of the native Cloud macros [^02^]. While they may function for now, Atlassian recommends replacing them with the **Jira Issues Macro** (type `/jira`) to ensure long-term compatibility [^02^].
Would you like the specific API query to search for these gadgets across your entire site?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.