-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Lens] avoid moving the aggregation location #78153
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
I agree that this is confusing, and I think I'd like to get @cchaos's opinion on how to improve it. The simplest approach is to stop changing the sort order of the functions, but if we do that without changing the styles we will get a "zebra-striping" effect. Maybe the zebra-striping is fine, and we should always keep the sort order the same. |
IMHO having a consistent order is more important than grouping the operations by applicability to the current field - the styling should be enough for that. |
@wylieconlon did you move this to "minor bugs" on purpose? Not sure how that matches with the |
@flash1293 I'm not sure what the right way to categorize this is, it's on the border between a bug and enhancement. I'd like to clean it up as soon as possible, potentially before the 7.10 feature freeze. |
Yep! I agree with these comments 💯 !! |
Let's call it a bug and fix it in the fix-it week. |
Describe the feature:
When moving between aggregations in Lens. Sometimes (not all times) the location of the aggregation changes after being clicked
It hurts the users' orientation. I realized something changed but IK wasn't sure what and why. To get expertise in Lens it is better to not move the location of the aggregation
In the gif see how the filter aggregation moves after clicked on.
The text was updated successfully, but these errors were encountered: