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

Vertical Bar Chart in "Normal mode" does not order split series correctly when "Descending" is selected #76496

Closed
swtrux opened this issue Sep 2, 2020 · 4 comments
Labels
blocked bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@swtrux
Copy link

swtrux commented Sep 2, 2020

Kibana version:
7.9.1
Elasticsearch version:
7.9.1

Server OS version:
RHEL Linux 3.10.0-1127.13.1.el7.x86_64

Browser version:
Firefox 80.0 (64-bit)

Browser OS version:
Windows 10.0.18363.0 (64-bit)

Describe the bug:
Vertical Bar Charts with a split series do not order items correctly when "Descending" or "Ascending" are selected for the "Order" in the split series. I believe this has been an issue for many versions as I can't remember when it worked correctly.

Steps to reproduce:
Create Vertical Bar Chart ordering the Buckets in Descending order, then split the series and also order it as descending. See images below for example with Metricbeat file system utilization split with mount points.

Expected behavior:
The split series should be ordered correctly. In my example the mount points should be shown ordered by percent full.

barchart
metrics
buckets
splitseries

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@stratoula stratoula added the Feature:Visualizations Generic visualization features (in case no more specific feature label is available) label Sep 2, 2020
@timroes
Copy link
Contributor

timroes commented Jul 22, 2021

Might be related to #14536

@timroes timroes added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Jul 22, 2021
@flash1293
Copy link
Contributor

Blocked by #86184

@flash1293 flash1293 added blocked impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Oct 13, 2021
@stratoula
Copy link
Contributor

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@stratoula stratoula closed this as not planned Won't fix, can't repro, duplicate, stale Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

5 participants