-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Meta] Share analytics across spaces #167901
Labels
Feature:Dashboard
Dashboard related features
impact:high
Addressing this issue will have a high level of impact on the quality/strength of our product.
Meta
Project:ShareToSpace
Team:Presentation
Presentation Team for Dashboard, Input Controls, and Canvas
Comments
ThomThomson
added
Feature:Dashboard
Dashboard related features
Team:Presentation
Presentation Team for Dashboard, Input Controls, and Canvas
labels
Oct 3, 2023
Pinging @elastic/kibana-presentation (Team:Presentation) |
Removing this from the project in favour of keeping the individual line items in. |
9 tasks
This was referenced Oct 9, 2023
This was referenced Nov 17, 2023
nickpeihl
changed the title
[Meta] Share dashboards across spaces phase 1
[Meta] Share analytics across spaces phase 1
Nov 29, 2023
2 tasks
timductive
added
Meta
impact:high
Addressing this issue will have a high level of impact on the quality/strength of our product.
labels
Nov 29, 2023
teresaalvarezsoler
changed the title
[Meta] Share analytics across spaces phase 1
[Meta] Share analytics across spaces
Nov 30, 2023
drewdaemon
added a commit
that referenced
this issue
Jan 16, 2024
## Summary The broken weak links problem wasn't fixed in 8.1, so this statement is now confusing. An aliasing workaround [was added](#149021) in 8.8 for those customers who need it. Better solutions - use the [new links panel](https://www.elastic.co/guide/en/kibana/current/dashboard-links.html) for navigation between dashboards - use [shareable dashboards](#167901) to make analytics stuff available in multiple spaces instead of copying (not yet available)
This was referenced Jan 26, 2024
Closed
Closed
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this issue
Feb 15, 2024
## Summary The broken weak links problem wasn't fixed in 8.1, so this statement is now confusing. An aliasing workaround [was added](elastic#149021) in 8.8 for those customers who need it. Better solutions - use the [new links panel](https://www.elastic.co/guide/en/kibana/current/dashboard-links.html) for navigation between dashboards - use [shareable dashboards](elastic#167901) to make analytics stuff available in multiple spaces instead of copying (not yet available)
👀 |
Closing, issue iceboxed in #188573 |
Linking a tactical option that could solve key pain points in the current flow of copying analytics objects between spaces: #176552 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Dashboard
Dashboard related features
impact:high
Addressing this issue will have a high level of impact on the quality/strength of our product.
Meta
Project:ShareToSpace
Team:Presentation
Presentation Team for Dashboard, Input Controls, and Canvas
Problems
Users can only share dashboards across spaces by copying them or exporting/importing wich create new copies of the dashboard and all its saved objects in the new space/s. When users update a dashboard or its related objects (dataviews, panels, linked dashboards) in a space, the changes will not be reflected in the rest of the spaces which creates different versions of the same objects generating confusion and mistrust in the results later on.
Requirements
Users would like to share dashboards across spaces so they have a centralize way to maintain the same dashboards in different spaces (i.e. one change in one dashboard is reflected in all the spaces containing this dashboard)
Must-haves
Milestone 1: Sharing API and UI
Milestone 2: Shareable files, maps, saved searches, annotation groups, and tags
Milestone 3: Shareable visualizations and Lens
Milestone 4: Shareable dashboard
Nice-to-have
Bugs
The text was updated successfully, but these errors were encountered: