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

Searching for a dashboard name only from the start #12600

Closed
monicasarbu opened this issue Jun 30, 2017 · 3 comments
Closed

Searching for a dashboard name only from the start #12600

monicasarbu opened this issue Jun 30, 2017 · 3 comments
Assignees
Labels
blocker bug Fixes for quality problems that affect the customer experience PR sent regression v6.0.0

Comments

@monicasarbu
Copy link

monicasarbu commented Jun 30, 2017

Kibana version: 6.0.0-alpha3-SNAPSHOT

Elasticsearch version: 6.0.0-alpha2

Browser version: Chrome

Description of the problem including expected versus actual behavior:

Steps to reproduce:

  1. Load dashboards in Kibana (one of them was Metricbeat: MongoDB)

  2. Get all the available dashboards under app/kibana#/dashboards
    screen shot 2017-06-30 at 3 34 40 pm

  3. Search for Mon and no results show up
    screen shot 2017-06-30 at 3 34 49 pm

Search works if you are searching for Metricbeat MongoDB:
screen shot 2017-06-30 at 3 59 49 pm

@thomasneirynck tested against Kibana 5.4.1 and it works perfectly, so it seems to be a regression.

@monicasarbu monicasarbu added Feature:Visualizations Generic visualization features (in case no more specific feature label is available) regression labels Jun 30, 2017
@thomasneirynck thomasneirynck added the bug Fixes for quality problems that affect the customer experience label Jun 30, 2017
@tylersmalley
Copy link
Contributor

tylersmalley commented Jun 30, 2017

@thomasneirynck, I believe this is caused by the change here: #12083

I would suggest surrounding the term with a wildcard *. We will need to do this for the saved objects management search, visualizations, dashboard, searches, etc.

@stacey-gammon
Copy link
Contributor

ah, thanks for finding that @tylersmalley. I wonder if changing search to search: search + '*' would be sufficient, in the saved_object_loader, then it would match previous functionality and be fixed for all types.

@tylersmalley
Copy link
Contributor

tylersmalley commented Jun 30, 2017

@stacey-gammon, I would prefer to include the wildcard where it's implemented if it's the intended behavior. That way we have the option of not using a wildcard without adding an additional option to find.

edit: Realized you mentioned making this change in the loader and not the client. Yes, I believe that would be a sufficient change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug Fixes for quality problems that affect the customer experience PR sent regression v6.0.0
Projects
None yet
Development

No branches or pull requests

6 participants