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

[Fleet]: Editing shared integration inconsistently doesn't show the new created policy in the confirmation flyout. #196795

Open
amolnater-qasource opened this issue Oct 18, 2024 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@amolnater-qasource
Copy link

Kibana Build details:

VERSION: 8.16.0-SNAPSHOT
BUILD: 79269
COMMIT: 574ec2fc5f383da6bff0d506cc6ab76803119dae

Preconditions:

  1. 8.16.0-SNAPSHOT Kibana cloud environment should be available.
  2. Shared integration should be installed in various policies.
  3. An agent should be installed.

Steps to reproduce:

  1. Navigate to Fleet>Agent policies tab.
  2. Update the shared integration- remove a few policies and add a few new policies.
  3. Also click Create a new agent policy.
  4. Click Save and observe flyout shows the new agent policy in the confirmation flyout.
  5. Click cancel now update the policy and add the removed policies again make more changes.
  6. Click create a new agent policy again.
  7. Observe the flyout doesn't show the new agent policy in the confirmation flyout.

Expected Result:
Editing shared integration should show the new created policy in the confirmation flyout.

Screen Recording:

Image

Agent.policy.2.-.Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2024-10-18.11-56-45.mp4

Feature:
#75867

@amolnater-qasource amolnater-qasource added bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Oct 18, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@muskangulati-qasource Please review.

@muskangulati-qasource
Copy link

Secondary review is Done for this ticket!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

3 participants