docs: note that dashboard controls follow the CPS scope (#7622) - #7677
Open
florent-leborgne wants to merge 1 commit into
Open
docs: note that dashboard controls follow the CPS scope (#7622)#7677florent-leborgne wants to merge 1 commit into
florent-leborgne wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Elastic Docs AI PR menuCheck 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. |
Contributor
🔍 Preview links for changed docs |
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses #7622 with the following changes:
explore-analyze/cross-project-search/cross-project-search-manage-scope.md: In the Dashboards row of the {{cps-init}} availability table, note that dashboard controls, such as Options list controls, suggest values from all projects in the selected {{cps-init}} scope, so readers comparing apps know controls follow the same scope as panels.explore-analyze/dashboards/using.md: In the dashboard-specific View data from multiple projects section, extend the "all panels update accordingly" statement to say that dashboard controls also suggest values from all projects in the selected scope. This section previously described panel behavior only, leaving the exact gap users hit when the old local-only control behavior changed.Both additions are serverless-only. The whole page and the target section are already scoped
serverless: preview/stack: unavailable, and no sibling table row carries a per-row badge, so no additionalapplies_totag is added (matching sibling scoping).Verification
The behavior is confirmed by the diff of elastic/kibana#276218: the Options list control now forwards the dashboard's
projectRouting(from the CPS scope) through its fetch path to Elasticsearch asproject_routing, and the client fetch cache keys includeprojectRoutingso switching the scope refetches instead of serving stale, origin-only values. No user-visible label was renamed; the change is backend routing only.Resolves
Closes #7622