Skip to content
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

[Feature request]Set default space and dashboard per user #35643

Closed
Sjaak01 opened this issue Apr 26, 2019 · 3 comments
Closed

[Feature request]Set default space and dashboard per user #35643

Sjaak01 opened this issue Apr 26, 2019 · 3 comments

Comments

@Sjaak01
Copy link

Sjaak01 commented Apr 26, 2019

Description
Enable setting a default space and dashboard at the user level inside Kibana.

Use case
We have a lot of dashboards (dozens) showing detailed information for certain situations and several Spaces. We also have a single dashboard in a Space that is used as a general overview, showing data based on which a user might move to a different dashboard to drill down on the data.

E.g. dashboards contain detailed error information for each location while the general dash shows which locations have errors.

Right now a user first has to select a space and then select the general dash. It would be much more convenient if we could specific a Space and dash to load by default.

@kobelb
Copy link
Contributor

kobelb commented Apr 26, 2019

Hey @Sjaak01, we have #25735 to track this request. Closing this as a duplicate.

@kobelb kobelb closed this as completed Apr 26, 2019
@GoodMirek
Copy link

The #25735 was not duplicate of this issue, see the latest comment there:

I think a per space level meets the requirements here. Once we have per user settings, we can open up another issue to track this.

Therefore, I think it was not correct to close this feature request.
Our company is ElasticCloud customer and we miss this feature.

@kobelb Any chance to reopen this feature request?

@GoodMirek
Copy link

Well, I found this issue is really duplicate, but of a different issue: #21640
Therefore, no need for reopening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants