docs: clarify computed field limitations for filtering and drilldowns (#6209)#6562
Open
florent-leborgne wants to merge 1 commit into
Open
docs: clarify computed field limitations for filtering and drilldowns (#6209)#6562florent-leborgne wants to merge 1 commit into
florent-leborgne wants to merge 1 commit into
Conversation
…#6209) Expand the existing ES|QL filtering note to also cover drilldown actions and the full set of computed-field cases (EVAL, STATS, Lens formulas, aggregation results). Add a matching limitation note to the drilldowns page and the ES|QL visualizations page. Co-authored-by: Cursor <cursoragent@cursor.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
✅ Vale Linting ResultsNo 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. |
nastasha-solomon
approved these changes
May 25, 2026
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
3 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 #6209 with the following changes:
explore-analyze/dashboards/using.md: Expanded the existing ES|QL filtering note (already scoped to stack 9.4 / serverless GA) to also cover drilldown actions and the full set of computed field cases: ES|QLEVALandSTATScolumns, Lens formulas, and aggregation results. The previous text only mentionedEVALand only mentioned filtering, not drilldowns.explore-analyze/dashboards/drilldowns.md: Added a prose sentence after the Requirements bullet list explaining that drilldowns cannot be triggered from computed field values, with a cross-link to the fuller explanation in Exploring dashboards.explore-analyze/visualize/esorql.md: Added a prose sentence in the "Add drilldowns" section noting thatEVALandSTATScolumn values do not support drilldowns, with a cross-link to Exploring dashboards.This acommpanies the UX improvement planned in elastic/kibana#260185 (showing disabled actions with a tooltip instead of silently hiding them)
Resolves
Closes #6209