Export a dashboard should export all viz's too

[markwalkom]

I couldn't find an existing issue on this one, but I may have missed it.

When you export a dashboard, the assumption is that it exports all aspects of it, including visualisations and searches. Currently this is not the case and you have to find and then export all related objects and then cat them into the one file.

It'd be a better experience if we did a single "contains everything" export.

[pemontto]

To be a complete export it would need to include index-patterns as well. I currently use a Python script to determine all dependencies of a dashboard down to the index pattern and push them to whatever destination.

[loekvangool]

And also scripted fields.

[tbragin]

@loekvangool we are tracking a separate ticket for exporting scripted fields: #5155

[tbragin]

@pemontto we are tracking a separate ticket for exporting index patterns: #4288

I agree a lot more is required to make JSON export/import complete

[GrahamHannington]

@tbragin wrote:

a lot more is required to make JSON export/import complete

+1

There are many things to like about the Elastic Stack, but the built-in support for exporting and importing dashboards and their related artifacts is not one of them.

Elastic 5 raises expectations. You develop a beautiful dashboard in Kibana and want to share it with others, and then you arrive here. I know what Immortan Joe would say 😜 .

[sta-szek]

+1

[GrahamHannington]

There’s a related Elastic discussion forum thread, “Deploying Kibana indexes, searches, visualization and dashboard in production”, to which I added a comment that is relevant to this issue.

(With apologies to @markwalkom and anyone else who has already seen that comment.)

[nreese]

Closing, saved object management now includes a toggle to "include related objects"