Skip to content
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

Show multiple agent policies on integration policies list UI #182111

Closed
3 tasks done
Tracked by #75867
juliaElastic opened this issue Apr 30, 2024 · 0 comments · Fixed by #186087
Closed
3 tasks done
Tracked by #75867

Show multiple agent policies on integration policies list UI #182111

juliaElastic opened this issue Apr 30, 2024 · 0 comments · Fixed by #186087
Assignees
Labels
QA:Needs Validation Issue needs to be validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@juliaElastic
Copy link
Contributor

juliaElastic commented Apr 30, 2024

Part of reusable integration policies work.

  • In Integrations page / integration policies list UI, the Agent policy column should show a count if there are multiple policy ids e.g. Agent policy 1 +1
  • The minimum privileges required to view this column should be Integrations:Read and Fleet: Agent policies:Read
  • The +1 count should be a link that opens a popover showing the list of agent policies and a Manage agent policies button
image
@juliaElastic juliaElastic added the Team:Fleet Team label for Observability Data Collection Fleet team label Apr 30, 2024
@juliaElastic juliaElastic changed the title Show count of agent policies on integration policies list UI Show multiple agent policies on integration policies list UI May 29, 2024
@kpollich kpollich added the QA:Needs Validation Issue needs to be validated by QA label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA:Needs Validation Issue needs to be validated by QA Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants