Export unsaved Explore state (chart builder) directly from Explore

What is the problem or goal the end user is trying to solve or accomplish?

Users, especially those with view-only access to production content, often tweak a chart in Explore to validate a hypothesis. They want to export that tweaked, unsaved state and import it into another workspace (e.g., a sandbox “Explore” workspace) without having to save a temporary chart in prod or go hunting in list views. Today this flow is slow, disruptive, and requires extra permissions (saving objects, finding names, navigating to list views).

How are they solving it currently?

• Save a temporary chart (requires edit/create permissions in the source workspace).

• Then navigate to Charts list → find by name → bulk/select → Export.

• Or manually recreate the same configuration in the destination workspace.

What is the recommended solution by the Customer?

Add an Export action to the Explore (chart builder) UI, under the “…” menu in the top-right, with two options:

• Export saved chart (current behavior, if chart is saved)

• Export current state (unsaved) → serializes the current form_data and metadata into a standard importable artifact (.zip/.json) without persisting a chart record.
  Additional notes/acceptance criteria:

• Works even when the user lacks “save” permissions.

• Uses the same import bundle format used by existing import/export so it’s compatible with cross-workspace imports.

• Includes dataset reference by UUID (and gracefully warns if the dataset doesn’t exist on import).

• Audit log should record that an Explore export occurred.

• Respect existing RBAC: introduce a specific permission (e.g., can_export_from_explore) if needed to control this capability for Viewers separately from Editors.