# Using a Discover Saved Search in a Dashboard does not show properly

**URL:** <https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747>\
**Category:** Kibana\
**Created:** [July 10, 2019, 11:46am UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747 "2019-07-10T11:46:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidnavalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidnavalho/32/49780_2.png) [@davidnavalho](https://discuss.elastic.co/u/davidnavalho)\
**Post date:** [July 10, 2019, 11:46am UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747/1 "2019-07-10T11:46:01Z")

</div>

We're adding a simple Saved Search from Discover into a Dashboard, but it does not seem to present data in the same manner it is presented in the actual Discover tab. Specifically, the un-expanded entries seem to be shown 1 word per line, instead of filling the whole image.

I've added a screenshot that clearly shows the issue. If there's another - nicer/better/alternative - method of showing logs as a visualization entry, I'm all up for it!

 ![dashboard-fail](https://us1.discourse-cdn.com/elastic/original/3X/c/2/c250369b771234f7386a2c09f0ba6c3174314d49.png)

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [July 10, 2019, 4:33pm UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747/2 "2019-07-10T16:33:01Z")

</div>

This is a [known issue](https://github.com/elastic/kibana/issues/35316) that will be resolved in the upcoming 7.3.0 release

---

<div class="post-metadata">

**Author:** ![davidnavalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidnavalho/32/49780_2.png) [@davidnavalho](https://discuss.elastic.co/u/davidnavalho)\
**Post date:** [July 11, 2019, 8:21am UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747/3 "2019-07-11T08:21:06Z")

</div>

Thanks for the reply. Any hint/method/shortcut on how to quickly get to the ~~Saved Search~~ Discover screen, based on the queries and filters currently set in adashboards, even if it was some sort of clickthrough? That would probably be the ideal scenario anyways!

---

<div class="post-metadata">

**Author:** ![davidnavalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidnavalho/32/49780_2.png) [@davidnavalho](https://discuss.elastic.co/u/davidnavalho)\
**Post date:** [July 11, 2019, 8:25am UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747/4 "2019-07-11T08:25:50Z")

</div>

Think I have a method, by following the hint at the bug report, to add our own columns. This works for now.

Thanks for the reply!

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [July 11, 2019, 12:51pm UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747/5 "2019-07-11T12:51:59Z")

</div>

That is not possible at the moment but you can follow [https://github.com/elastic/kibana/issues/12560](https://github.com/elastic/kibana/issues/12560) for updates

---

<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:** [August 8, 2019, 12:52pm UTC](https://discuss.elastic.co/t/using-a-discover-saved-search-in-a-dashboard-does-not-show-properly/189747/6 "2019-08-08T12:52:01Z")

</div>

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