-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet]: 'Tags' label is not shown on the Dashboards page #142554
Comments
Pinging @elastic/fleet (Team:Fleet) |
Secondary Review is done |
Pinging @elastic/kibana-presentation (Team:Presentation) |
@juliaElastic The tags were moved to be part of the first column in this PR, so the behaviour you are seeing on @elastic/shared-ux Any insight on why the tags might not be showing up in this case? |
This does not appear to be an issue anymore in 8.6.0+. |
Hi @nickpeihl We have revalidate this ticket on released 8.6.1 Kibana build and found it still reproducible. Video here for reference is attached: Dashboards.-.Elastic.-.Google.Chrome.2023-02-14.18-24-43.mp4Hence, we are reopening this issue. Thanks |
Reassigning this to @elastic/appex-sharedux because they own the table list view component. Likely they will close this, as the lack of a separate tags column is an intentional change. Additionally, in the video, it looks like the tags are showing up properly. |
@dikshachauhan-qasource Going to close this one, the tags are visible, just in a different place. |
Thank you @jen-huang for the feedback. We can close this issue as per intended tags display view. |
Kibana version: 8.5 Kibana Staging environment
Host OS and Browser version: All, All
Build Details:
Preconditions:
Steps to reproduce:
Managed
,System
andElastic Agent
Tags should be shown.Dashboards
page.Tags
label is not shown.Expected Result:
Tags
label should be shown onDashboards
page as per ticket [Fleet] Add "managed" and integration name tags to Saved Objects installed by EPM #123904Screen Recording and Screenshots:
Dashboards.-.Elastic.-.Google.Chrome.2022-10-04.10-08-42.mp4
The text was updated successfully, but these errors were encountered: