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

Incorrect sorting on Storagesize when viewing data streams #86122

Closed
legrego opened this issue Dec 16, 2020 · 1 comment · Fixed by #86204
Closed

Incorrect sorting on Storagesize when viewing data streams #86122

legrego opened this issue Dec 16, 2020 · 1 comment · Fixed by #86204
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@legrego
Copy link
Member

legrego commented Dec 16, 2020

Kibana version: 7.10.0

Describe the bug:

When viewing data streams from the Index Management app, you have the option to sort by storage size within the UI. This will sort the items in the data streams list alphabetically rather than by the actual storage size.

Expected behavior:

The list should be sorted by storage size instead of alphabetically

@legrego legrego added bug Fixes for quality problems that affect the customer experience Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Dec 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

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:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants