Add Feature Controls to All Visualization Editors

[alexfrancoeur]

We have numerous visualization editors in Kibana and the list will continue to grow (#36148). While this speaks to the true power of Kibana, it can sometimes be confusing for new users. It would be nice for an administrator to have the option to define which editor their end users should be using.

This request is specifically around adding feature controls to all visual editors. Today, we already have them for Timelion and Maps (dashboard embeddability coming soon, so it counts now 😉 ), and I imagine Lens will get this out of the box. Ideally, the Time Series Visual Builder and our classic Visualize visualizations would also have feature controls.

[elasticmachine]

Pinging @elastic/kibana-app

[legrego]

It sounds like toggling specific visualization types would benefit from having "sub features", where the main "Visualize" feature could, for example, have a set of its own toggles to determine which viz types are allowed. If I'm thinking about this correctly, then we're tracking that in #35616

[timroes]

@legrego the only thing we could keep in mind when it gets to "sub features" in that sense is: that the actual visualize app has no idea what it sub features (in this case vis types) are, since they are all coming from individual (maybe even not installed, or third party) plugins. So if we would have a "sub features"-feature, this would only work for us, if we can actually register a sub feature "from the outside" to an existing feature.

[stratoula]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.