Conversation
| plugins.contentManagement.favorites.registerFavoriteType('dashboard'); | ||
|
|
||
| // Register dashboard in content management for search functionality | ||
| plugins.contentManagement.register({ |
There was a problem hiding this comment.
This is not the correct path. We removed content management because we want all interfacing with dashboards to go through the "dashboards as code" REST API. If your plugin depends on dashboard plugin, use findDashboardService search method exposed from the dashboard public start contract. If your plugin can not depend on dashboard plugin (because of circular dependencies), then use UI action searchDashboardAction. Here is an example of using the search action https://github.com/elastic/kibana/blob/main/src/platform/plugins/shared/presentation_util/public/components/dashboard_picker/dashboard_picker.tsx#L48
There was a problem hiding this comment.
I replaced contentManagement service with UiActions. I tested it locally and works. Let me know what you think
nreese
left a comment
There was a problem hiding this comment.
Would it be possible to remove entire src/platform/packages/shared/dashboards/dashboards-selector package and just use https://github.com/elastic/kibana/blob/main/src/platform/plugins/shared/presentation_util/public/index.ts#L22? This package is very duplicative of what already exists.
Is it possible to select multiple dashboards with the That was the main reason why the |
src/platform/packages/shared/dashboards/dashboards-selector/services/dashboard_service.ts
Outdated
Show resolved
Hide resolved
...tform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.test.tsx
Outdated
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Outdated
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Outdated
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Outdated
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Outdated
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Outdated
Show resolved
Hide resolved
src/platform/packages/shared/dashboards/dashboards-selector/components/dashboards_selector.tsx
Outdated
Show resolved
Hide resolved
src/platform/plugins/shared/content_management/public/content_client/content_client.tsx
Outdated
Show resolved
Hide resolved
92ad275 to
4434c0c
Compare
It was a mistake to put this component into its own package. Instead, this component should be a part of presentation-util-plugin. I have opened #243668 to track the issue |
5455bc5 to
7a0d454
Compare
7a0d454 to
9409d9c
Compare
|
@cesco-f Thanks for the review. I think I applied all your feedback. I'll do one more scan and then I will open it up for review. |
nreese
left a comment
There was a problem hiding this comment.
kibana-presentation changes LGTM
code review only
| @@ -0,0 +1,41 @@ | |||
| /* | |||
There was a problem hiding this comment.
Can you rename file to get_dashboards_by_ids_action to match export getDashboardsByIdsAction
| }); | ||
|
|
||
| const results = await Promise.all(dashboardPromises); | ||
| // Fetch dashboards by their IDs directly instead of fetching all dashboards |
There was a problem hiding this comment.
not sure comment is needed since it describes a change that no longer exists in the code base. This comment should be removed.
There was a problem hiding this comment.
Verified locally.
- dashboards are visible in the dropdown
- while creating rule from
dashboardsoro11y > rulespage - while editing rules from
o11y > rulespage
- while creating rule from
- not visible
- while creating/editing rule from
stack management > rulesorsecurity solution > rulespage
- while creating/editing rule from
|
@cesco-f I am trying to run the failing Synthetics tests locally, I get this error:
On CI the |
|
@js-jankisalvi Thanks for testing it out.
We actually want the related dashboards dropdown to be visible in the Stack Managamanet > Rules page as well. This was a bug, that I fixed in this commit |
Able to see and select dashboards while creating/editing rule from stack management > rules 👍 |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
History
|
Fixes elastic#243350 This PR fixes the issue where, no dashboards come up in the list when trying to link dashboards to a rule. Before <img width="1068" height="237" alt="515720113-9e346ea0-d5f6-4ef8-be8e-07db7d65743f (1)" src="https://github.com/user-attachments/assets/97cf3e1f-a8bb-46e5-a99a-2b74e2689015" /> **After** <img width="839" height="237" alt="Screenshot 2025-11-19 at 13 44 08" src="https://github.com/user-attachments/assets/86af5081-c71b-4b29-96ea-dae630681bba" /> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Fixes elastic#243350 This PR fixes the issue where, no dashboards come up in the list when trying to link dashboards to a rule. Before <img width="1068" height="237" alt="515720113-9e346ea0-d5f6-4ef8-be8e-07db7d65743f (1)" src="https://github.com/user-attachments/assets/97cf3e1f-a8bb-46e5-a99a-2b74e2689015" /> **After** <img width="839" height="237" alt="Screenshot 2025-11-19 at 13 44 08" src="https://github.com/user-attachments/assets/86af5081-c71b-4b29-96ea-dae630681bba" /> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

Fixes #243350
This PR fixes the issue where, no dashboards come up in the list when trying to link dashboards to a rule.
Before

After
