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

[Lens] Remember last used index pattern on startup #61757

Closed
timroes opened this issue Mar 30, 2020 · 3 comments · Fixed by #69511
Closed

[Lens] Remember last used index pattern on startup #61757

timroes opened this issue Mar 30, 2020 · 3 comments · Fixed by #69511
Assignees
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@timroes
Copy link
Contributor

timroes commented Mar 30, 2020

Lens should remember the last used index pattern (at least within the browser) when starting the app.

@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens :Lens/basic-expectation labels Mar 30, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@wylieconlon
Copy link
Contributor

We have talked about this a bit, and it seems like this is more like an editor preference that should be stored in localstorage, so that each user can resume from their previous state.

It does not belong in the URL because index patterns can change when going from Lens -> Dashboard and back.

@wylieconlon
Copy link
Contributor

When opening a previously-saved Lens object in the editor, we already open the index patterns that were being used. As long as this behavior doesn't overlap with this case, I think the fallbacks are:

  1. Use the saved doc if available
  2. Use the localstorage saved index pattern
  3. Use the default index pattern

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants