Sub-aggregations should be sorted globally

[bgoldowsky]

Describe the feature:

Currently, a visualization with sub-buckets such as a heat map, if both the X and Y axes have a natural order, there is no way to get both axes to sort in the expected way. The sub-aggregations are sorted within the scope of each main bucket. I believe they should instead be sorted globally according to the chosen sort criteria (or, if there is a use case where the current behavior is preferable, this should be a user option).

Example:
(from https://discuss.elastic.co/t/ordering-for-both-axes-of-heatmap/104589 )

Here is a heatmap. The "class" and "investigation number" are both numeric values which ought to be presented in order:

As you can see the Y "class" axis is not in the ascending order by term as I wanted.
I can give the Y axis priority so that it does appear in the correct order like this:

But now the investigation number is not in increasing order. There is currently no way to get both axes in the expected order.

[guanghaofan]

yes, is there any plan to fix this issue asap?

[s9gf4ult]

Vote for this issue as well.

[symstopje]

+1

[matthew-hickok]

+1....Please!

[Kaiserchen]

+1

[bodinsamuel]

+1

[zxytim]

+1
I encountered the same issue today, and thought it was just a "google, and you are all set" thing. But later I was quite surprised that this issue was raised 1 year ago, and has been lying here since then.
Hope to see some actions regarding this issue.

[MarcelViennyTech]

+1

[chenmach]

+1

[lubobill1990]

+1 I think the heatmap chart can be used a lot when we hope to find relationship between two variables.

If there's one variable that's randomly listed, the relationship can hardly be find, which makes heatmap meaningless.

---

Maybe, vega is for this requirement?

[ghost]

+1 on this. Attempting to create a heatmap for common monitor sizes, it's very difficult to view this data property without being able order both axes correctly.

[zivklara]

+1
having the same issue in Vertical Bar. is it going to be fixed soon?
I would like to sort by field1, and color by field2. for more info and examples, please view this thread

[rwhit]

+1
Why is this an enhancement and not just a straight up bug? Heatmaps where both axes have a natural order are common - and not very useful if one of the axis is sorted randomly.

[jbjose]

+1

[MichaelWCC]

+1

In all my use cases I could just simply set the order manually, that would be a great improvement. I get what happens behind the scenes but it's tedious every time someone else encounters the problem and I have to explain why the plot is screwed up. Just like lubobill1990 says, it's hard to see some patterns when the second agg is all over the place.

[ambim]

+1

Trying to create a pretty rudimentary HourOfDay by DayOfWeek heatmap and can't

I also agree with @rwhit . It is a bug, as the UI suggests to the User that it is possible to sort by both X & Y axes, when in fact it's not.

[ambim]

This has now been an Open issue for 25 months, any update @timroes ?

[dk-data]

+1
Does anyone have a viable workaround for this in the absence of a fix?

[toopricey]

If you use the Extend Bounds functionality, it will cause (numerical) values to be correctly ordered. I'm unsure if this works for non-numeric ordering.

[karnamonkster]

+1

[ch-bas]

+1

[lachlann562]

This is not just on heatmaps, the same problem happens with line graphs as well.

[flash1293]

Duplicate of #86184

[PaoloUr]

+1

[FrancescoUrbano]

+20