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

Navigating to Enterprise Search apps breaks solution layout for other apps #108191

Closed
joshdover opened this issue Aug 11, 2021 · 5 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience Team:EnterpriseSearch

Comments

@joshdover
Copy link
Contributor

Kibana version: 7.14.0

Elasticsearch version: 7.14.0

Server OS version:

Browser version: Chrome 92.0

Browser OS version: mac OS 11.5.1

Original install method (e.g. download page, yum, from source, etc.): Cloud ESS

Description of the problem including expected versus actual behavior:

Navigating to the either the App Search or Workplace Search applications and then to another solution such as Security or Observability breaks the solution-nav on the left side in the other apps. Only happens when navigating to App Search or Workplace Search first

Steps to reproduce:

  1. Create 7.14.0 cluster on ESS
  2. Open App Search or Workplace Search app
  3. Open Security Solution app

image

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Describe the feature:

@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 11, 2021
@joshdover joshdover added bug Fixes for quality problems that affect the customer experience Team:AppSearch and removed needs-team Issues missing a team label labels Aug 11, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/workplace-search-frontend (Team:WorkplaceSearch)

@elasticmachine
Copy link
Contributor

Pinging @elastic/app-search-frontend (Team:AppSearch)

@cee-chen
Copy link
Contributor

#107973 fixes this and was recently merged into master/7.x. @joshdover would you like us to backport this to 7.14.1 as well? When I checked with @cchaos, I believe she asked for 7.15 only, but I'm definitely happy to backport.

@joshdover
Copy link
Contributor Author

Great, yes I hadn't tested on master. Unless there's a reason a backport wouldn't work, I think we should backport. Generally, any bug fix should be backported since users are more likely to upgrade to patch releases than minors.

I'll go ahead and close this.

@cee-chen
Copy link
Contributor

Awesome, thanks! I'll get started on that 7.14.1 backport now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:EnterpriseSearch
Projects
None yet
Development

No branches or pull requests

4 participants