Skip to content

CPS: Dashboard-level scope and panel-level custom scope badge#5428

Merged
florent-leborgne merged 25 commits intocps-tech-previewfrom
cps/690-691-dashboards-cps
Mar 23, 2026
Merged

CPS: Dashboard-level scope and panel-level custom scope badge#5428
florent-leborgne merged 25 commits intocps-tech-previewfrom
cps/690-691-dashboards-cps

Conversation

@florent-leborgne
Copy link
Contributor

@florent-leborgne florent-leborgne commented Mar 10, 2026

Summary

Adds CPS documentation to the dashboard pages, split by audience:

For dashboard viewers (using.md):

  • New "View data from multiple projects" subsection under "Search and filter your dashboard data"
  • Explains how the CPS scope selector controls which projects the dashboard queries
  • Documents the "Custom CPS scope" badge on panels that use project routing

For dashboard creators (create-dashboard.md):

  • Adds Store CPS scope with dashboard to the settings list (step 5) and save options (step 6)
  • Restructures the save step with a comprehensive list of all save options
  • Updated screenshot of the save dialog

Closes elastic/docs-content-internal#690
Closes elastic/docs-content-internal#691

Test plan

  • Verify pages build correctly at explore-analyze/dashboards/using and explore-analyze/dashboards/create-dashboard
  • Confirm applies_to tags render properly (serverless preview / stack unavailable)
  • Check cross-links to CPS pages resolve correctly (depend on sibling CPS branches)
  • Verify "Store CPS scope with dashboard" label matches Kibana UI (confirmed, fix in Align save modal CPS label with settings flyout kibana#259142)

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 (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used: Claude (Cursor)

Made with Cursor

Add a section explaining that alerting rules use the space-level CPS
scope (not a per-rule setting), and that the project picker is
read-only on rule pages.

Closes #688

Made-with: Cursor
@github-actions
Copy link
Contributor

github-actions bot commented Mar 10, 2026

✅ Vale Linting Results

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 10 commits March 10, 2026 18:14
Add a new "Cross-project search scope" section to the dashboard usage
page covering dashboard-level CPS scope storage and per-panel custom
CPS scope badges. Also add the CPS settings option to the dashboard
creation page and a brief CPS badge section to the panel management page.

Closes #690, closes #691

Made-with: Cursor
The save modal label is being updated from "Store project routing with
dashboard" to "Store CPS scope with dashboard" in elastic/kibana#259142.

Made-with: Cursor
Remove alerting, observability rules, and security detection rules CPS
content that was added by mistake. This PR focuses on dashboard-level
CPS scope and panel-level custom CPS scope badge only.

Made-with: Cursor
- using.md (viewer): keep scope selector and badge explanation, remove
  store instructions, link to creator page
- create-dashboard.md (creator): expand store CPS scope into a full
  section with settings flyout and save modal instructions
- manage-panels.md (creator): explain why the badge appears, which
  panel types support it, and how to edit from the popover

Made-with: Cursor
Nest the CPS section as a subsection of "Search and filter your
dashboard data" with a verb-led heading matching sibling sections.
Rewrite content from the viewer's perspective: what they see, what
they can change, and why some panels behave differently.

Made-with: Cursor
The viewer's scope selector controls which projects are queried by
default, not the creator's setup. Remove misleading sentence and
reframe around what the viewer sees and can do.

Made-with: Cursor
Structure the CPS section as default behavior first, then two bullet
points for the outlier cases (stored scope, custom badge). Fix the
inline anchor to use valid MyST target syntax.

Made-with: Cursor
List all save options as bullet points for scannability. Move ownership
note under Permissions. Replace "modal" with plain language.

Made-with: Cursor
The setting is already explained in both step 5 (settings flyout) and
step 6 (save options). The standalone section was duplicating that
content. Update cross-links accordingly.

Made-with: Cursor
The badge appears automatically and requires no panel management
action. The viewer perspective is already covered in using.md, and
the Edit action is a shortcut to the existing Edit visualization flow.

Made-with: Cursor
@florent-leborgne florent-leborgne marked this pull request as ready for review March 23, 2026 17:38
@florent-leborgne florent-leborgne requested review from a team as code owners March 23, 2026 17:38
@florent-leborgne florent-leborgne merged commit 7406e08 into cps-tech-preview Mar 23, 2026
8 checks passed
@florent-leborgne florent-leborgne deleted the cps/690-691-dashboards-cps branch March 23, 2026 18:57
florent-leborgne added a commit to elastic/kibana that referenced this pull request Mar 24, 2026
## Summary

The dashboard settings flyout uses **"Store CPS scope with dashboard"**
but the save modal uses **"Store project routing with dashboard"**. This
aligns the save modal label and tooltip to use the same user-facing CPS
terminology as the settings flyout.

Additionally, both the save modal tooltip and the settings flyout help
text are aligned to use the same concise phrasing, spelling out
"cross-project search (CPS)" instead of just "CPS".

### Changes

- Save modal label: "Store project routing with dashboard" → "Store CPS
scope with dashboard"
- Save modal tooltip: Aligned with settings flyout phrasing, spelling
out "cross-project search (CPS)"
- Settings flyout help text: Shortened and aligned with the save modal
tooltip

### Context

Found while reviewing CPS documentation
([docs-content#5428](elastic/docs-content#5428)).
The inconsistency was spotted by cross-referencing the two UI surfaces
against the Kibana source.

Made with [Cursor](https://cursor.com)
@mbondyra
Copy link
Contributor

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.

3 participants