[Research] UIState Per-panel Removal

[clintandrewhall]

Summary of Exploration or Proposed Change

the uiState key is currently used to store inconsequential dashboard panel specific information. This includes whether or not to show the legend, and the color scheme.

As part of the Inline Editing project, it was decided that we would remove the existing UiState key in order to simplify where state is stored for embeddables, and minify the number of variables associated with panel editing in a dashboard.

Findings

Removing the UiState from the dashboard panels would be a fairly straightforward change. Many of the use cases that this covers, can be covered better with By Value panels.

Why is this a breaking change
If a cluster has multiple color customizations for the same by reference chart on different dashboards, those color customizations will be lost on upgrade. Migrating to keep these changes will not be possible without unlinking the panels from the library, which would not be an ideal solution.

• Proposed Priority: Medium
• Level of Effort: Medium
• Dependencies:
  • Dependencies on Kibana App to ensure that they are able to cover all the existing use cases.
• Proposed development: 7.14

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[ThomThomson]

Closing this as UIState is currently removed from the Dashboard code and has been for some time. It only exists in the explicitInput of certain embeddable types - and those embeddable types are in change of their own state.