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] Fix breadcrumb to include Lens #62167

Closed
timroes opened this issue Apr 1, 2020 · 7 comments
Closed

[Lens] Fix breadcrumb to include Lens #62167

timroes opened this issue Apr 1, 2020 · 7 comments
Labels
Feature:Lens good first issue low hanging fruit Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@timroes
Copy link
Contributor

timroes commented Apr 1, 2020

Fix global breadcrumbs to include Lens. So Visualize / Create should become Visualize / Lens / Create

@timroes timroes added Feature:Lens good first issue low hanging fruit Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Apr 1, 2020
@elasticmachine
Copy link
Contributor

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

@lpeixotoo
Copy link

@timroes
I'm willing to start contributing to kibana, is Lens open to community contributions?

@timroes
Copy link
Contributor Author

timroes commented Apr 15, 2020

Hi @lpeixotoo,

Lens is as all our code open for community contribution, and community contributions are always highly welcome 💚

As long as noone is assigned to an issue here it should mean no one is yet working on it. If you have interest working on something, just drop a note, and we can assign you to it. If you will drop it again, please make sure to leave another note, so we can unassign you from that issue again.

Cheers,
Tim

@lpeixotoo
Copy link

@timroes,

That's great! I can try to address this one, would be a pleasure to help with.

@flash1293
Copy link
Contributor

@timroes Is this something we still want?

@timroes
Copy link
Contributor Author

timroes commented Feb 5, 2021

I'd forward that to the @ryankeairns since that issue came mostly out of central design/header consideration.

@ryankeairns
Copy link
Contributor

Given that we are steering customers toward Lens - and doing so with preference to a dashboard-first workflow (as opposed to Visualize > Lens) - I do not think this particular change would be a Product preference. For that reason, I would be in favor of closing this issue.

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

No branches or pull requests

5 participants