Skip to content
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] Heatmap problem with colouring cells with value equal to the min value #117512

Closed
stratoula opened this issue Nov 4, 2021 · 3 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure :VisEditors:fix-it-week

Comments

@stratoula
Copy link
Contributor

Describe the bug:
I create a lens heatmap and I see that if a cell has a metric value equal to the min value of the bands, then it is not coloured correctly.

image

Here the color of the right cell shpuld be blue but is transparent instead

@stratoula stratoula added bug Fixes for quality problems that affect the customer experience Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Nov 4, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors (Team:VisEditors)

@dej611
Copy link
Contributor

dej611 commented Nov 4, 2021

This can be easily replicated via the kibana_sample_data_flights dataset, using the Cancelled field for the Horizontal axis and the AvgPricePerTicket as metric/cell value.

What happens is that the value is something like 491.688888881111 or similar, but the color ranges generated are rounded up to the second decimal digit 492.69 and this makes the comparison fail, leaving the cell without color.
Note that heatmap has a color continuity set to above by default, which filter any value lower than the minimum, hence the behaviour.

A possible solution is to compute the raw value, without rounding, at least in percentage mode.

@mbondyra
Copy link
Contributor

Closing because it's fixed in #116170 cc @dej611

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure :VisEditors:fix-it-week
Projects
None yet
Development

No branches or pull requests

5 participants