opensearch-project / OpenSearch-Dashboards

📊 Open source visualization dashboards for OpenSearch.
https://opensearch.org/docs/latest/dashboards/index/
Apache License 2.0
1.66k stars 870 forks source link

[BUG] Saved search panel in a dashboard doesn't correctly display less than 5 items #6532

Open alison-mtsi opened 5 months ago

alison-mtsi commented 5 months ago

Describe the bug

A saved search panel in a dashboard does not accurately display less than 5 objects when filters are applied. When one object should be present, nothing is displayed. When 2-4 objects are present, an unexpected scroll bar appears regardless of the size of the query panel; user is unable to view all of them without scrolling.

To Reproduce Steps to reproduce the behavior:

  1. Go to Discover, select an index
  2. Select any number of fields to view
  3. Save the search (Save > Save search)
  4. Add saved search to a new or existing dashboard
  5. Add a filter to down select to 1-5 specific results

If step 5 is replicated in the Discover tab for the index, the filtering accurately displays the desired items. Only when the saved query is placed within a dashboard does the behavior seem to happen.

Expected behavior Visually the saved search should be identical to the results in the Discover tab.

OpenSearch Version AWS GovCloud Managed service, latest - 2.11

Plugins None

Screenshots Note: one item should be present but is not visible. Scrollbar appears but scrolling does not display any item. saved-query-panel-on-dashboard-1-item

Four items should be visible, but only three are. Scroll bar appears and must scroll to see fourth item. saved-query-panel-on-dashboard-4-items

Host/Environment (please complete the following information):

Additional context

Add any other context about the problem here.

I'm using OpenSearch as a managed service in AWS GovCloud. I reported this problem to AWS Support; they were able to reproduce on their end but directed me to submit a bug report here.

kavilla commented 5 months ago

@ananzh is this resolved in 2.13?