Skip to content

docs: export individual dashboard panels as JSON (#7611) - #7956

Open
florent-leborgne wants to merge 13 commits into
mainfrom
docs/7611-export-panel-json
Open

docs: export individual dashboard panels as JSON (#7611)#7956
florent-leborgne wants to merge 13 commits into
mainfrom
docs/7611-export-panel-json

Conversation

@florent-leborgne

@florent-leborgne florent-leborgne commented Aug 13, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds a technical preview procedure for exporting an individual dashboard panel's JSON configuration in Serverless and planned Stack 9.6+.
  • Documents the panel types currently opted in, the unpinned-control limitation, and the Show full configuration behavior for library-linked panels.
  • Clarifies that panel exports exclude dashboard-level filters and the global time range but include visualization-owned context; control exports include their current selections.
  • Shows the panel menu and Export JSON action in a screenshot at the first procedure step.
  • Clarifies that panel export provides only the panel configuration and offers copy or download actions. It does not offer Open in Console, which remains part of the complete dashboard export flow.
  • Excludes Vega because its product support is still unmerged.

Closes #7611.

Product sources reviewed: elastic/kibana#273427, elastic/kibana#281795, and current Kibana main. Product PR #273427 merged to main with the v9.6.0 label before the 9.6 branch cut.

Validation

  • GitHub documentation build, Vale, applicability, and link checks passed
  • Buildkite documentation preview passed
  • Local git diff --check passed
  • Local Vale reported no findings on changed lines; two pre-existing warnings remain on lines 2 and 105
  • Screenshot source and repository image checksums match
  • Cumulative applies_to, content type, frontmatter, and link checks
  • Isolated fresh-reader review, passed after one correction round

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No
  1. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used.

Tool(s) and model(s) used: OpenAI Codex (GPT-5). Used to triangulate the docs issue and related product work, verify the current implementation, draft the change, and run documentation checks.

AI-Assisted: OpenAI Codex (GPT-5)
@github-actions

github-actions Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
Comment thread explore-analyze/dashboards/sharing.md Outdated
Comment thread explore-analyze/dashboards/sharing.md Outdated

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs review summary

Focus areas

  • Style and clarity: Mostly solid; one inline comment on a list-punctuation/Oxford-comma inconsistency in the new "Export a panel as JSON" section.
  • Jargon: None found — panel/control/library terms are already used consistently elsewhere on the page.
  • Frontmatter and applies_to: New section-level applies_to block (stack: preview 9.6+, serverless: preview) is correctly placed directly under the heading with no blank line, matches the linked issue's stated availability (Stack v9.6.0 preview, Serverless preview), and doesn't conflict with the page-level ga tag since it's properly scoped to the new section.
  • Content type fit: Fits the existing how-to page structure; the new section follows the same pattern as sibling "Export JSON" section (intro paragraph, numbered steps, screenshot).
  • Contradictions: No contradictions found against published docs or the rest of this page.
  • Parent issue satisfaction: Satisfied — the PR adds the panel-level Export JSON entry point, describes the Show full configuration switch for library-linked panels, and clarifies scope differences (filters/time range) as requested in #7611.

Notes

  • Pre-existing Vale warning on line 2 (mapped_pages) is untouched by this PR and out of scope for this review.

Generated by Docs review agent for #7956 · sonnet50 · 40.5 AIC · ⌖ 6.5 AIC · ⊞ 17.1K

Comment thread explore-analyze/dashboards/sharing.md Outdated
florent-leborgne and others added 2 commits August 13, 2026 21:00
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Comment thread explore-analyze/dashboards/sharing.md Outdated
Comment thread explore-analyze/dashboards/sharing.md Outdated
Comment thread explore-analyze/dashboards/sharing.md Outdated
Comment thread explore-analyze/dashboards/sharing.md Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Export an individual panel as JSON from the panel menu

1 participant