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.

Sign up for GitHub

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

Jump to bottom

[Fleet] Include Fleet Sub feature access in warning pop-up messages #181226

Open
karanbirsingh-qasource opened this issue Apr 19, 2024 · 3 comments
Open

[Fleet] Include Fleet Sub feature access in warning pop-up messages #181226

karanbirsingh-qasource opened this issue Apr 19, 2024 · 3 comments
Assignees
@nchaulet
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Elastic-Agent-Control-Plane Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@karanbirsingh-qasource
Copy link

Describe the bug:
Include Fleet Sub feature access in warning pop-up messages

Kibana/Elasticsearch Stack version

Version: 8.14.0 SNAPSHOT
Commit: 9369f3a4df8a10ccf5e293ff7410e3688cb567d0
Build: 73512

precondition

  • Custom Role should be created with below config

image

Steps to reproduce

  • Login to Kibana
  • Navigate to Fleet Page
  • Helpful banner details are incorrect or incomplete
  • Mentioned feature access is already given in role still we are getting this warning banner

image

Current Result

  • Fleet Sub feature access is missing in warning pop-up messages

Expected Result

  • Only giving All access to Fleet Feature is not sufficient, user need to give All/Read access to sub feature also
    So there should be mention of Fleet Sub feature also

image

Screen-Shot:

image
@karanbirsingh-qasource karanbirsingh-qasource added the bug Fixes for quality problems that affect the customer experience label Apr 19, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 19, 2024
@karanbirsingh-qasource karanbirsingh-qasource added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Apr 19, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 19, 2024
@amolnater-qasource amolnater-qasource removed their assignment Apr 19, 2024
@amolnater-qasource
Copy link

Secondary review for this ticket is Done

@kpollich
Copy link
Member

Thanks - we should enhance the wording on this error for sure, but this a low priority improvement at this time. Adding to a future sprint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nchaulet nchaulet

Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Elastic-Agent-Control-Plane Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ycombinator @nchaulet @kpollich @elasticmachine @karanbirsingh-qasource @amolnater-qasource