# Filter Tabbing and Auto-Completion in 7.x

**URL:** <https://discuss.elastic.co/t/filter-tabbing-and-auto-completion-in-7-x/217238>\
**Category:** Kibana\
**Created:** [January 30, 2020, 3:59pm UTC](https://discuss.elastic.co/t/filter-tabbing-and-auto-completion-in-7-x/217238 "2020-01-30T15:59:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Micah\_Hunsberger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/micah_hunsberger/32/147436_2.png) [@Micah\_Hunsberger](https://discuss.elastic.co/u/Micah_Hunsberger)\
**Post date:** [January 30, 2020, 3:59pm UTC](https://discuss.elastic.co/t/filter-tabbing-and-auto-completion-in-7-x/217238/1 "2020-01-30T15:59:38Z")

</div>

In Kibana 6.x, when you add a filter, you would automatically switch from field name, operator, and values as soon as you entered a value. In 7.x, I have to hit tab 2 or 3 times to go from field name to operator, or from operator to values.

There also seems to be less support for giving value suggestions in the value section of the filters. Kibana 6.x wasn't perfect, and often was missing some field values as suggestion, but generally it worked. In 7.x, I almost always get "There are no options available", or I have to wait several seconds before getting a dropdown of possible options.

Did Kibana change how this list is populated? Are only certain field names or index patterns supported for autocomplete?

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [January 30, 2020, 6:21pm UTC](https://discuss.elastic.co/t/filter-tabbing-and-auto-completion-in-7-x/217238/2 "2020-01-30T18:21:40Z")

</div>

@Bargs you want to grab this question?

Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![Micah\_Hunsberger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/micah_hunsberger/32/147436_2.png) [@Micah\_Hunsberger](https://discuss.elastic.co/u/Micah_Hunsberger)\
**Post date:** [January 30, 2020, 9:11pm UTC](https://discuss.elastic.co/t/filter-tabbing-and-auto-completion-in-7-x/217238/3 "2020-01-30T21:11:44Z")

</div>

After some more testing, it seems to work more consistently for smaller indices than the larger ones. I see that in version 7.5 there are these two settings in Kibana:

> `kibana.autocompleteTimeout:`
> 
> **Default: "1000"** Time in milliseconds to wait for autocomplete suggestions from Elasticsearch. This value must be a whole number greater than zero.
> 
> `kibana.autocompleteTerminateAfter:`
> 
> **Default: "100000"** Maximum number of documents loaded by each shard to generate autocomplete suggestions. This value must be a whole number greater than zero.

Do these apply to filters, the search bar, and options list visualization, or just one of them?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 27, 2020, 9:16pm UTC](https://discuss.elastic.co/t/filter-tabbing-and-auto-completion-in-7-x/217238/4 "2020-02-27T21:16:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.