Summary
Site Optimizer’s Custom fields → Clean up custom fields view does not provide any “Export” capability. Jira admins need an option to export the full table to CSV so they can analyze the data offline and share it with stakeholders who don’t have access to Site optimizer or Jira admin.

Steps to Reproduce

1. As a Jira admin, go to ⚙️ Settings → System → Site optimizer → Custom fields.
2. Under Clean up custom fields, click Review and clean up (or Update then scroll to the table).
3. Observe the table listing unused/trashable custom fields and their metrics (name, type, usage, recommendations, etc.).
4. Look for an option to export this table (CSV / Excel / download).

Expected Results

• There is a clear Export option (for example, “Export to CSV”) on the Clean up custom fields table.

• Clicking Export downloads a CSV including all visible rows and columns (e.g. field name, ID, type, recommendation, where used/contexts, etc.).

• Admins can:

• Perform offline analysis (sorting, filtering, pivoting, aggregations).

• Share the file with teams or stakeholders who don’t have Site optimizer or Jira admin access (e.g. governance, security, business owners).

• Ideally, export respects current filters/search so admins can export just the subset they’re reviewing.

Actual Results

• There is no built‑in export option on the Clean up custom fields table.

• Admins must manually copy the table from the browser (sometimes in multiple chunks, with zoom adjustments) into a spreadsheet and then save/export as CSV.

• This is time‑consuming and error‑prone, especially on sites with hundreds of custom fields, and not suitable for regular/recurring analysis.

Workaround

• Log in as Jira admin and open Site optimizer → Custom fields → Clean up custom fields.

• Manually select the table (often requiring browser zoom at ~75% and copying in several parts).

• Paste into a spreadsheet application (e.g. Numbers, Excel, Google Sheets).

• Clean up column headers/formatting and then export the sheet as CSV.

• Alternatively, advanced admins can use browser developer tools to capture the underlying JSON behind the table and convert that to CSV, but this relies on internal/undocumented APIs and is not user‑friendly.