Visualization / Search Count to Dashboard Relation

[jerodwaldman]

Describe the feature:
As we continue to change and add visualizations and saved searches to our system, we'd like to keep a handle on visualizations and saved searches that are obsolete. An extremely useful way to do this is either at the saved object view or the visualization / saved searches view, there could be a column that displays how many dashboards that visualization / saved search is included on.

One other approach that would actually be even more beneficial would be to have an "analytics" module that can tell you how many views a certain visualization, dashboard, saved search, etc... is getting per time period (hour, day, week, month, etc...)

Describe a specific use case for the feature:
Nearly 100% of the time when we build out a visualization or saved search, it gets included into a dashboard. However, we sometimes build new ones to replace older views leaving some obsolete saved objects on our system. Having to dig through dozens of dashboards and hundreds of visualizations to manually mix and match which ones are related to which is time consuming. I'd like to get another sortable column that tells me how many dashboards any saved object is related to so I can quickly identify unused or obsolete views our team is no longer using.

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[TBretherton]

At the moment I'm trying to get rid of old visualizations that are no longer being used. It would be really handy to be able to easily see how many times a given visualization is used in a dashboard on the saved objects section.

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[pgayvallet]

An extremely useful way to do this is either at the saved object view or the visualization / saved searches view, there could be a column that displays how many dashboards that visualization / saved search is included on

The savedObjects management 'edition' view is going to be deprecated soon, and is only meant to be a 'raw' representation display of a given SO attributes. Enhancing this page with per-so-type features is really something that should not be considered as an option.

[pgayvallet]

We have a few initiatives in progress toward that direction, with issues more up to date than this one.

I'll close this in favor of #186530