-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed dashboard nested fields filtering #4425
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-1.2-wzd 4.4-1.2-wzd
# Navigate to the new working tree
cd .worktrees/backport-4.4-1.2-wzd
# Create a new branch
git switch --create backport-4425-to-4.4-1.2-wzd
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 850646e58c9cf6ee74538af23d0a2cf7b0655df3
# Push it to GitHub
git push --set-upstream origin backport-4425-to-4.4-1.2-wzd
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-1.2-wzd Then, create a pull request where the |
* Added missing index pattern to queries * Added changelog (cherry picked from commit 850646e)
* Added missing index pattern to queries * Added changelog (cherry picked from commit 850646e)
Description
In the dashboards, nested fields were not properly identified and because of this, the query results didn't work as expected. To fix it we added the index pattern information to the query building methods, so the field information can be retrieved and analyzed to structure the query object.
Closes #4430