Hello @mikewillis
I believe that search is not possible as it contains - as part of the ID.
opened 11:59AM - 23 Jan 23 UTC
Team:Core
Feature:Saved Objects
Team:SharedUX
There are several places where the Kibana UI allows users to search over their s… aved objects:
1. Management
1. Saved objects
2. Data views
3. Tags
4. Cases
2. Dashboard list
3. Visualize library
We have received feedback from users that the search experience does not meet their expectations. There have also been several attempts to solve this each only making it incrementally better. This issue is to discuss how we might provide users with a world class search experience powered by the saved objects APIs.
I suggest the following steps to be able to make progress against this problem:
1. Identify the combination of search query, text analyser and mappings that provide the best possible search experience on the raw Elasticsearch APIs
2. Ensure that it's possible to use the above combination for saved object types using the server-side saved objects client.
3. Create a guide for teams to ensure their saved object types have everything needed to power a powerful search experience and adapt the UI if/where needed.
#### Related issues:
- https://github.com/elastic/kibana/issues/9767
- https://github.com/elastic/kibana/issues/14729
- https://github.com/elastic/kibana/issues/97074
- https://github.com/elastic/kibana/issues/32776
- https://github.com/elastic/kibana/issues/90315
- https://github.com/elastic/kibana/issues/22051
- https://github.com/elastic/kibana/pull/15175
- https://github.com/elastic/kibana/issues/5734
- https://github.com/elastic/enhancements/issues/17002
- https://github.com/elastic/kibana/issues/151007
opened 06:24PM - 04 Feb 21 UTC
Team:Core
enhancement
Feature:Saved Objects
**Describe the bug:**
According to the documentation [1], the `search` proper… ty in the saved object find options is supposed to support Elasticsearch simple query string [2] syntax. However, the saved object finder doesn't properly parse and send the query you type in when using negated syntax.
**Steps to reproduce:**
1. Install sample data
2. Go to Stack Management > Saved Objects
3. Try to filter out results by putting a `-` in front of a clause
The clause ends up being filtered *for*, rather than *against*.
**Screenshots (if relevant):**
https://user-images.githubusercontent.com/1178348/106937786-69925200-66db-11eb-8375-b48db2e420ac.mov
**Any additional context:**
It looks like the bug might be where we use only the text portion of the query and ignore the "must_not" portion of the generated AST [3].
[1] https://github.com/elastic/kibana/blob/0f45439a5fd882e0503979c84f1a8a333e695a79/src/core/server/saved_objects/types.ts#L81-L82
[2] https://www.elastic.co/guide/en/elasticsearch/reference/7.10/query-dsl-simple-query-string-query.html
[3] https://github.com/elastic/kibana/blob/0f45439a5fd882e0503979c84f1a8a333e695a79/src/plugins/saved_objects_management/public/lib/parse_query.ts#L24-L27
Thanks!!