-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] unable to add last value of date/string field #104787
Labels
enhancement
New value added to drive a business result
Feature:Lens
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Comments
tsullivan
added
the
bug
Fixes for quality problems that affect the customer experience
label
Jul 8, 2021
tsullivan
added
Feature:Lens
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Jul 8, 2021
Pinging @elastic/kibana-app (Team:KibanaApp) |
flash1293
added
enhancement
New value added to drive a business result
and removed
bug
Fixes for quality problems that affect the customer experience
labels
Jul 8, 2021
+1
|
+1 for date but also string should be supported for last state type of use cases. |
flash1293
changed the title
[Lens] unable to add last value of date field
[Lens] unable to add last value of date/string field
Jan 14, 2022
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
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Kibana version: 7.14.0-bc1
Original install method (e.g. download page, yum, from source, etc.): docker
Describe the bug:
Input validation prevents the user from configuring a table in Lens from showing the last value of a date field.
Steps to reproduce:
email
field in the table. Lens creates a "Top values of email" table:The date fields are in light gray text. When you click on one of them, the function automatically changes to "Unique count".
The same limitation happens with
Maximum
andMinimum
. Looks like that is already filed as an issue: #95489Expected behavior:
"Last value of date" should be supported.
The text was updated successfully, but these errors were encountered: