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] Improve XY boundary extends popup layout #127853

Closed
Tracked by #184459
dej611 opened this issue Mar 16, 2022 · 2 comments
Closed
Tracked by #184459

[Lens] Improve XY boundary extends popup layout #127853

dej611 opened this issue Mar 16, 2022 · 2 comments
Labels
enhancement New value added to drive a business result Feature:Lens 🧊 iceboxed 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

@dej611
Copy link
Contributor

dej611 commented Mar 16, 2022

since you are talking about bounds i'd like to propose a simplification and adjustment of the UI to what is currently done by other tools:
we don't necessary need to have a big switch to choose between full extent (including zero), data extent (possible without zero), and custom.
We can show always two numeric inputs: one for the min and one for the max of the range: when you enter a value this will become a configured value, the default (empty) field instead is the min or max of the data.
Adding a small switch we can specify if we want to force the range to include the zero or not. This should be default on and disabled when using bars/areas, but is enabled and can be switched off on lines.

Screenshot 2022-03-10 at 13 26 04

I'm proposing this because:

  • the term Full doesn't clearly describe that we are covering the data extent including the zero
  • the term Data bounds or Data is not super clear to me

Originally posted by @markov00 in #126943 (comment)

@dej611 dej611 added enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Mar 16, 2022
@elasticmachine
Copy link
Contributor

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

@stratoula stratoula added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jan 16, 2023
@stratoula stratoula added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Jun 2, 2023
@markov00
Copy link
Member

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box #184459

@markov00 markov00 closed this as not planned Won't fix, can't repro, duplicate, stale May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Lens 🧊 iceboxed 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

4 participants