Skip to content

docs: rework import dashboards for the Dashboards API workflow and move it under Manage dashboards (#7166)#7185

Open
florent-leborgne wants to merge 12 commits into
mainfrom
docs-issue-7166-import-rework
Open

docs: rework import dashboards for the Dashboards API workflow and move it under Manage dashboards (#7166)#7185
florent-leborgne wants to merge 12 commits into
mainfrom
docs-issue-7166-import-rework

Conversation

@florent-leborgne

Copy link
Copy Markdown
Member

Summary

This PR addresses #7166 with the following changes:

  • explore-analyze/dashboards/import-dashboards.md: restructured into an applies-switch mirroring the Export JSON section of the sharing page. The 9.4+/serverless tab routes by use case (copy to space for same-deployment moves; the Dashboards API and manage-as-code for cross-deployment or code-based workflows) and demotes NDJSON import to a "still available, not recommended" note; the 9.0–9.3 tab keeps the current Saved Objects NDJSON import steps.
  • explore-analyze/toc.yml: moved import-dashboards.md and sharing.md under Managing dashboards (out of Build a dashboard and the top level).
  • explore-analyze/dashboards.md: updated the "Import a dashboard" description to match the new framing.

Resolves

Closes #7166

Depends on

Notes for reviewers

  • No redirects were added: re-nesting pages in toc.yml doesn't change their URLs (the URL derives from the file path, which is unchanged), so the redirects.yml entries the issue anticipated aren't needed.
  • building.md already drops the old "import ... exported from another instance" bullet in docs: add manage dashboards as code overview (#5448) #7029, so it isn't touched here.
  • The page keeps applies_to: stack: ga / serverless: ga at the page level; the version split lives in the applies-switch, matching the sharing page.

Screenshots to add or update

  • explore-analyze/dashboards/import-dashboards.md — the existing NDJSON import screenshot (kibana-dashboard-import-saved-object.png) now sits inside the 9.0–9.3 tab. It's still accurate for that path; no update needed unless the Saved Objects import UI changes.

AI-generated draft — created with Claude Opus 4.8.
Review all generated content for factual accuracy before merging.

Split the import page into an applies-switch mirroring the Export JSON
section: a 9.4+/serverless tab that routes to copy-to-space and the
Dashboards API / manage-as-code, and a 9.0-9.3 tab that keeps the Saved
Objects NDJSON import. Move import and sharing under Managing dashboards.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

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

  • Review docs changes (docs-review). Status: not started.

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

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Jul 3, 2026

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.

florent-leborgne and others added 2 commits July 8, 2026 18:31
…oards API

Rework the intro to present why you would import a dashboard, and reframe
the 9.4+ tab so the Dashboards API is the primary import flow. Demote
copy-to-space to a secondary aside for same-deployment moves.

Co-authored-by: Cursor <cursoragent@cursor.com>
Replace the version-based applies-switch with a tab set named by the
exported format (JSON via Dashboards API, NDJSON via Saved Objects).
Reframe the intro around how the dashboard was exported, give each tab
clear prerequisites, and lean on the export page for the concepts.

Co-authored-by: Cursor <cursoragent@cursor.com>
…pace

Point to the import saved objects API from the NDJSON tab and the copy
saved objects to space API from the copy note, so every UI path also
shows its programmatic form.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@florent-leborgne florent-leborgne marked this pull request as ready for review July 9, 2026 12:50
@florent-leborgne florent-leborgne requested review from a team as code owners July 9, 2026 12:50

@bmorelli25 bmorelli25 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

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.

Rework "Import a dashboard" for the Dashboards API workflow (applies-switch) and move it under Manage dashboards

2 participants