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: "Break down by" field is not formatted #61968

Closed
flash1293 opened this issue Mar 31, 2020 · 3 comments · Fixed by #63288
Closed

Lens: "Break down by" field is not formatted #61968

flash1293 opened this issue Mar 31, 2020 · 3 comments · Fixed by #63288
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens regression Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@flash1293
Copy link
Contributor

flash1293 commented Mar 31, 2020

When using a "Break down by" dimension, the formatter for the field is not applied - instead the raw value is used.

This is especially visible when using a datehistogram aggregation
Screenshot 2020-03-31 at 14 56 34

But it also happens for other field types (e.g. using a static lookup formatter on a string field and doing a terms aggregation).

Works fine when applied to the x axis

Also I would probably expect to be able to use the inline number formatting options in case I'm working with a numeric field (like when I'm defining a y axis):

Screenshot 2020-03-31 at 15 00 56

@flash1293 flash1293 added bug Fixes for quality problems that affect the customer experience Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Mar 31, 2020
@elasticmachine
Copy link
Contributor

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

@mbondyra
Copy link
Contributor

mbondyra commented Apr 9, 2020

Looks like this is also related, although not sure if caused by the same thing. When having two layers and the second one is time-based, time is not being formatted either:

image

@wylieconlon
Copy link
Contributor

@mbondyra I think the issue you found is not caused by the same thing. The issue reported by Joe is probably caused by this change: #60708

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 regression Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants