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

[Security Solution] [Bug] Wrong successful message with error notification pop up on adding a wrong format file under bulk import for knowledge base #196096

Open
muskangulati-qasource opened this issue Oct 14, 2024 · 6 comments · May be fixed by #205075
Assignees
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:Obs AI Assistant Observability AI Assistant Team:Observability Team label for Observability Team (for things that are handled across all of observability) triage_needed v8.16.0

Comments

@muskangulati-qasource
Copy link

Describe the bug
Wrong successful message with error notification pop up on adding a wrong format file under bulk import for knowledge base

Kibana/Elasticsearch Stack version

VERSION: 8.16.0
BUILD: 78825
COMMIT: a805375758e4bc931cf13dfdcac89b8d877a15d2

Steps

  1. Kibana version 8.16.0 or above should exist without endpoints
  2. Navigate to Stack management under Management section
  3. Navigate to Kibana >> AI Assistants
  4. Click on Manage settings for Elastic AI Assistant for Observability
  5. Navigate to the Knowledge base tab
  6. Click on the icon for new entry
  7. Add a wrong extension file
  8. Observe the error notification pops up and the successful message is also shown to the user

Expected Result
There should be a notification message for successful deletion

Screen Recording

AIAssistantImportError.mp4
@muskangulati-qasource muskangulati-qasource added 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: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v8.16.0 labels Oct 14, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@muskangulati-qasource
Copy link
Author

@amolnater-qasource please review!!

@amolnater-qasource
Copy link

Reviewed & assigned to @MadameSheema

@MadameSheema MadameSheema added the Team:Security Generative AI Security Generative AI label Oct 14, 2024
@peluja1012 peluja1012 added Team:Observability Team label for Observability Team (for things that are handled across all of observability) and removed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Dec 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/unified-observability (Team:Observability)

@peluja1012 peluja1012 added Team:obs-knowledge Observability Experience Knowledge team and removed Team:Security Generative AI Security Generative AI labels Dec 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-knowledge-team (Team:obs-knowledge)

@emma-raffenne emma-raffenne added Team:Obs AI Assistant Observability AI Assistant and removed Team:obs-knowledge Observability Experience Knowledge team labels Dec 16, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant)

@emma-raffenne emma-raffenne removed their assignment Dec 16, 2024
@viduni94 viduni94 self-assigned this Dec 22, 2024
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:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Obs AI Assistant Observability AI Assistant Team:Observability Team label for Observability Team (for things that are handled across all of observability) triage_needed v8.16.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants