-
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
[Data view] Default geo-field #120799
Comments
Pinging @elastic/kibana-gis (Team:Geo) |
Pinging @elastic/kibana-app-services (Team:AppServicesUx) |
This doesn't sound difficult but we could use more details about what is desired and how it might work from a UX perspective. Also, how does this relate OKRs / larger goals? So we can prioritize this correctly. |
I see this as a natural follow-up to the concept of a default time field in data views but for the spatial dimension; that is, wherever a UI element can benefit from accessing the geospatial aspect of a data view.
I'd say this feature aligns with the objective of improving users' experience. My 🪙 🪙 |
Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment. |
This issue was triggered as a potential task to improve usability of the Maps app. I think it's OK to reopen and keep it around. |
Pinging @elastic/kibana-presentation (Team:Presentation) |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed. |
Describe the feature:
Data views have a default time-field. It would be great if users could configure a default geo field.
Describe a specific use case for the feature:
This would be incredibly useful to be able to create default Maps (similar how Kibana can show default time-series visualizations).
e.g. automatically show a map in Lens, Discover, ....
The text was updated successfully, but these errors were encountered: