Skip to content

Add package version 3 guidance for legacy visualization errors #1479

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/howto/update_major_package_spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,23 @@ There are two variants of this error:
between different dashboards, and to allow users to quickly filter using the
query bar without affecting the provided filters.

### "My Dashboard" contains legacy visualization: "My Visualization" (metric, TSVB)

All visualizations must be created using [Lens](https://www.elastic.co/kibana/kibana-lens) or [Vega](https://www.elastic.co/guide/en/kibana/current/vega.html).

The only exceptions are
- markdown panels created from the dashboard application
- TSVB markdown. Support will eventually be removed, but this is
currently allowed because we do not yet offer an alternative for
injecting analytics into markdown. Prefer the dashboard markdown
panels since there are no plans to deprecate those.

Most legacy visualizations can be converted by selecting "Convert to Lens"
from the dashboard panel context menu or by clicking "Edit visualization in Lens"
after opening the visualization in the editor.

The legacy "input-control-vis" must also be replaced by the new [dashboard controls](https://www.elastic.co/guide/en/kibana/current/add-controls.html).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These visualizations are the ones allowed in this PR elastic/package-spec#619 ?

It could be removed, but I guess it also gives some hint to remove those visualizations. What do you prefer to do here @drewdaemon ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! I added those to the exceptions.


## Troubleshooting upgrades to Package Spec v2

### field (root): Additional property license is not allowed
Expand Down