Dashboard lists columns for searches: does not reflect updates to columns in saved search

[GrahamHannington]

Perhaps this is working as designed, but it tripped me up (Kibana 4.1.0, build 7467).

1. I saved a dashboard that included a saved search.
2. I opened the saved search, added a column to its Documents table, and then saved the updated search.
3. I opened the dashboard, expecting to see the search with the new column. Nope, not there.

I looked at the JSON of the dashboard definition, and could see why that column was missing: the object in the dashboard definition for the search contains a "columns" property that lists the columns for the search. That list reflects the columns in the saved search when I added the search to the dashboard.

I considered editing the dashboard definition JSON to insert the missing column; I even considered deleting the "columns" property, to see if Kibana would default to using the (latest) set of columns in the saved search. In the end, though, I played safe, and simply deleted that search from the dashboard, re-added the search, and then saved the updated dashboard.

Is this - saving the columns of a search's Documents table in a dashboard definition - working as designed? Could I have simply deleted that "columns" property from the corresponding object in the dashboard definition JSON, or would that cause problems? (I haven't tried that; I need to move on.)

[w33ble]

Could I have simply deleted that "columns" property from the corresponding object in the dashboard definition JSON, or would that cause problems? (I haven't tried that; I need to move on.)

I believe that would work, but I'm not sure, and that shouldn't be required. This is definitely a bug, the saved search updates if you re-add it, and should update automatically.

[lukasolson]

Side note, saved visualizations on dashboards DO update when you update the corresponding saved visualization. So yeah, definitely a bug.

[PavelVanecek]

Just ran into this issue using Kibana 4.4 (dev build from commit 26fce6e). Removing the search from dashboard and adding it back helped.

[anhlqn]

I really don't want to remove and readd a saved search to every dashboard whenever I update that saved search. Yet directly editing dashboard JSON is a workaround for me.

[kobelb]

When a saved search is added to the dashboard, the columns are copied to the dashboard's JSON. It appears this is to support the user deleting/moving columns from the dashboard, without them affecting the underlying saved search.

Should we consider modifying the underlying saved search when this modification occurs via the dashboard?

[tbragin]

Closing as dup of #9523