-
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
URL field formatter: Better integration with links to Kibana #53763
Comments
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Also related to #4338 |
Highly related to #12560 for general drill down improvements |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner. |
Describe a specific use case for the feature:
I use the URL field formatter very heavily to link between different parts of Kibana. This is very useful when using the field value e.g. as a filter parameter.
But there are two problems with this at the moment that makes it hard to work with it.
1.) To use the field value as a filter value for the dashboard, the user has to manually replace the necessary URL parts with the {{value}} placeholder. This is hard to understand for users that just started to use Kibana.
2.) If a user just copies the URL of the dashboard and do the replacement it will always guide to this version of the dashboard. When the users updates the dashboards afterwards the user has to recreate the link. This takes a lot of time.
Describe the feature:
Provide help for creating links to Kibana internal objects when using the URL field formatter. E.G. add a dropdown with the list of available dashboards. And let the user decide to use the field value as filter in a simple intuitive way.
Ideally being able to jump to any part of Kibana without copy / paste the URL.
@shaunmcgough
The text was updated successfully, but these errors were encountered: