# Drop down filter for long fields cut off

**URL:** <https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368>\
**Category:** Kibana\
**Created:** [September 29, 2020, 2:06pm UTC](https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368 "2020-09-29T14:06:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![luminance](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luminance/32/76380_2.png) [@luminance](https://discuss.elastic.co/u/luminance)\
**Post date:** [September 29, 2020, 2:06pm UTC](https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368/1 "2020-09-29T14:06:00Z")

</div>

It is very frustrating when you work with fields with longer name. The drop down fields for the filter become unusable, so you have to memorize all the field names by heart, or hovering over all of them one by one. Here is a great example:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/3/33506a25d82458f4ebf879a402c5793d623da39f.png)

That means that almost all searches in `metricbeat-*` index-pattern become such an infuriating experience.

On top of that, selecting a wrong field cannot be edited. When you try that, the whole search field is erased, so you have to go through the whole process of finding the correct field again.

Is that the worst modern UI design ever?

This is the same for Kibana 6.x, 7.x, plus now I am trying out the 8.x themed view, and there is no difference.

Any solution for this?

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [September 30, 2020, 5:57am UTC](https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368/3 "2020-09-30T05:57:54Z")

</div>

Here is a PR which addresses this concern . Please let us know if this what you were looking for:

> <https://github.com/elastic/kibana/pull/38971>

cc @kertal

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![luminance](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luminance/32/76380_2.png) [@luminance](https://discuss.elastic.co/u/luminance)\
**Post date:** [September 30, 2020, 8:26am UTC](https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368/4 "2020-09-30T08:26:27Z")

</div>

Hi @rashmi, this PR is referring to the "main" search/filter field. The issue that I've pointed out was the **Add filter** Drop down menu (as seen in the picture).

---

<div class="post-metadata">

**Author:** ![Marta\_Bondyra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marta_bondyra/32/102122_2.png) [@Marta\_Bondyra](https://discuss.elastic.co/u/Marta_Bondyra)\
**Post date:** [October 12, 2020, 11:39am UTC](https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368/5 "2020-10-12T11:39:19Z")

</div>

Hi @luminance thanks for raising it. If you want our developers to hear your voice, you can submit a bug/feature request in our github repository: [https://github.com/elastic/kibana/issues/new/choose](https://github.com/elastic/kibana/issues/new/choose) – that's the most effective way to reach out the proper team and also to track the issue.  
Best,  
Marta

---

<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:** [November 9, 2020, 11:39am UTC](https://discuss.elastic.co/t/drop-down-filter-for-long-fields-cut-off/250368/6 "2020-11-09T11:39:27Z")

</div>

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