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

[Security Solution] [Bug] Wrong placeholders for the new index entry under the knowledge base #196093

Closed
muskangulati-qasource opened this issue Oct 14, 2024 · 4 comments
Closed

[Security Solution] [Bug] Wrong placeholders for the new index entry under the knowledge base #196093

muskangulati-qasource opened this issue Oct 14, 2024 · 4 comments
Assignees
@peluja1012 @jamesspi
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.16.0

Comments

@muskangulati-qasource
Copy link

Describe the bug
Wrong placeholders for the new index entry under the 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 Security
  5. Navigate to the Knowledge base tab
  6. Click on the icon to add new >> Index
  7. Observe the placeholders are wrong

Expected Result
The placeholders should be correct

Screenshot
Image
@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
@muskangulati-qasource
Copy link
Author

Hi @MadameSheema,

We have tested this ticket on the latest SNAPSHOT build and found the issue to be fixed 🟢

Please find below the testing details.

ESS

Build details

VERSION: 8.16.0
BUILD: 79135
COMMIT: 1a3efcceb40a5a6c5ee55a44c3fe7642206008e5

Screenshot

Image

Hence, we are closing this ticket and marking it as fixed and QA Validated.

Thanks!

@muskangulati-qasource muskangulati-qasource added fixed QA:Validated Issue has been validated by QA and removed triage_needed labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@peluja1012 peluja1012

@jamesspi jamesspi

Labels
bug Fixes for quality problems that affect the customer experience fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.16.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@peluja1012 @elasticmachine @MadameSheema @jamesspi @muskangulati-qasource @amolnater-qasource