-
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
Template service for Kibana document title #35210
Comments
Pinging @elastic/kibana-platform |
Another request that just came through was to show the active filters in the dashboard title. |
👀 I know this isn't a super important feature, but it would really be nice to have this. We have multiple instances on Elastic Cloud, and when both Kibana tabs are open, it is very easy to mistake one for the other. |
@joshdover is this now the application service is available somewhere on the roadmap or linked as part of it? |
Nothing exists in the New Platform yet, but we have opened this issue: #46077 which is yet to be prioritized. One of the ideas that came up is leveraging the information already present in breadcrumbs to populate the document title automatically. |
@joshdover have we decided to not implement this, or is this now tracked buy some other issue? |
We have a couple of issues and users asking for changing the document title. Some want to get rid of the dashboard name (#19468), some want more distinction or in general customization in the name (#31250).
I think to enable this we should enable two things:
window.title
setting). The user could then specify something like${page} - ${app} - Kibana (Dev)
, and then would get a title likeMy Dashboard - Dashboard - Kibana (Dev)
in that case.document.title
to set those, which would not work in that scenario anymore. I would suggest we're creating a core service, that you can then call from everywhere to set the value of those placeholders, so e.g. when opening a dashboard I would callcore.document.setTitle({ app: 'Dashboard', page: 'My Dashboard' })
, and this service would then use the configured template to build the title.I would suggest the following placeholders to start with:
${app}
- App name (Dashboard, Visualize, Uptime, Management) - would be specified by the call to the core API${page}
- Page name (My Dashboard/Vis Name, subpage like "Advanced Setting") - would be specified by the call to the core API${space}
- Current Space name${user}
- Current user name${instance}
(or the like) - maybe some configurable instance name that can be specified in thekibana.yml
The text was updated successfully, but these errors were encountered: