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.

Sign up for GitHub

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

Jump to bottom

After upgrade from 8.15.3 to 8.16.0 TSVB line chart ignores "point size" #200255

Closed
robcowart opened this issue Nov 14, 2024 · 1 comment · Fixed by #202358
Closed

After upgrade from 8.15.3 to 8.16.0 TSVB line chart ignores "point size" #200255

robcowart opened this issue Nov 14, 2024 · 1 comment · Fixed by #202358
Assignees
@markov00
Labels
bug Fixes for quality problems that affect the customer experience regression Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@robcowart
Copy link

Kibana version: 8.16.0

Elasticsearch version: 8.16.0

Server OS version: Ubuntu 24.04

Original install method (e.g. download page, yum, from source, etc.): Docker

Describe the bug: After upgrade from 8.15.3 to 8.16.0 TSVB ignore

Steps to reproduce:

Create a TSVB visualization line chart and set point size to 0. It has to be set to a negative value to disappear.

Screenshots (if relevant):

8.15.3...

Image

post 8.16.0 upgrade...

Image
@robcowart robcowart added the bug Fixes for quality problems that affect the customer experience label Nov 14, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 14, 2024
@mbondyra mbondyra added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Nov 15, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-visualizations (Team:Visualizations)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 15, 2024
@markov00 markov00 self-assigned this Nov 27, 2024
@markov00 markov00 mentioned this issue Nov 29, 2024
Merged
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Dec 3, 2024
@markov00
[TSVB] fix point visibility regression (elastic#202358)
4a1f90c 
## Summary

fix elastic#200255

The regression was caused by a [breaking
change](elastic/elastic-charts#2525) introduced
by elastic-charts around the `area.points.visible` style, that passed
from a `boolean` to a union of `'always' | 'never' | 'auto'`;

(cherry picked from commit a7397b2)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Dec 3, 2024
@markov00
[TSVB] fix point visibility regression (elastic#202358)
40ac3fa 
## Summary

fix elastic#200255

The regression was caused by a [breaking
change](elastic/elastic-charts#2525) introduced
by elastic-charts around the `area.points.visible` style, that passed
from a `boolean` to a union of `'always' | 'never' | 'auto'`;

(cherry picked from commit a7397b2)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Dec 3, 2024
@markov00
[TSVB] fix point visibility regression (elastic#202358)
f69deb6 
## Summary

fix elastic#200255

The regression was caused by a [breaking
change](elastic/elastic-charts#2525) introduced
by elastic-charts around the `area.points.visible` style, that passed
from a `boolean` to a union of `'always' | 'never' | 'auto'`;

(cherry picked from commit a7397b2)
hop-dev pushed a commit to hop-dev/kibana that referenced this issue Dec 5, 2024
@markov00 @hop-dev
[TSVB] fix point visibility regression (elastic#202358)
4941fe1 
## Summary

fix elastic#200255

The regression was caused by a [breaking
change](elastic/elastic-charts#2525) introduced
by elastic-charts around the `area.points.visible` style, that passed
from a `boolean` to a union of `'always' | 'never' | 'auto'`;
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 9, 2024
@markov00 @CAWilson94
[TSVB] fix point visibility regression (elastic#202358)
ce9a758 
## Summary

fix elastic#200255

The regression was caused by a [breaking
change](elastic/elastic-charts#2525) introduced
by elastic-charts around the `area.points.visible` style, that passed
from a `boolean` to a union of `'always' | 'never' | 'auto'`;
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
@markov00 @CAWilson94
[TSVB] fix point visibility regression (elastic#202358)
b91188f 
## Summary

fix elastic#200255

The regression was caused by a [breaking
change](elastic/elastic-charts#2525) introduced
by elastic-charts around the `area.points.visible` style, that passed
from a `boolean` to a union of `'always' | 'never' | 'auto'`;
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markov00 markov00

Labels
bug Fixes for quality problems that affect the customer experience regression Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[TSVB] fix point visibility regression markov00/kibana
4 participants
@markov00 @mbondyra @robcowart @elasticmachine