-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Discover] Allow user to specify display names for fields #47659
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
This would be a great feature! |
I'd like to chime in here - I'd love to see this feature, I think it would make Kibana UI's a lot more accessible and user friendly. |
+1 Would love to see it. |
+1 |
1 similar comment
+1 |
On a related topic, the pop-up text for fields should be revised to show the full field name. Per the screenshot above it becomes impossible to select amongst fields when their names are hidden under the fold, and that is typically the case. Currently the pop-up text displays the field type, but that is useless additional data as the type is already shown by the type icon. I guess ideally, the type name pop-up should be preserved for the type icon, and the full field name should pop-up for the abbreviated field name. |
This comment has been minimized.
This comment has been minimized.
We display saved searches in all our dashboards and the column headings are long, nested strings that the user doesn't need to know about. End-users don't need to know that a value is nested 3 levels deep, they just need a useful column name. |
When you work on this, please follow the OWASP guidelines and prevent fields from starting with characters that would allow for script injection. Possible overlap with Kibana-56081 |
Custom field names are now supported. Closing the issue. |
This is a follow up of #1896, focusing on discover. With the introduction of the new EUI data grid, we should take care of letting the user define custom labels for fields. Our data often contains nested fields which lead to long titles like
level1FieldName.level2Fieldname.level3Fieldname
in Discover. It should be possible to define a custom label like
awesomeLevel3
.The text was updated successfully, but these errors were encountered: