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

Error message when searching in Incidents / Knowledge / Attack patterns #6551

Closed
Filigran-Automation opened this issue Apr 3, 2024 · 0 comments
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Filigran-Automation
Copy link
Member

Description

An error message appears "An unknown error occurred" when searching for a specific Attack patterns in Incidents / Knowledge / Attack patterns.

Environment

OpenCTI version: Demo OpenCTI 6.0.8

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to Incidents tab
  2. Click on Knowledge
  3. Click on Attack Patterns in the menu on the right side of the screen.
  4. Go on the Search bar, and type any Attack Pattern name
  5. Error message appears "An unknown error occurred"

Expected Output

The platform display the Attack patterns names that match the search.

Actual Output

Error message appears "An unknown error occurred"

Additional information

Screenshots (optional)

Capture d'écran 2024-04-03 095957
Capture d'écran 2024-04-03 100029

@Filigran-Automation Filigran-Automation added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Apr 3, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.10 milestone Apr 3, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Apr 4, 2024
@marieflorescontact marieflorescontact self-assigned this Apr 5, 2024
@marieflorescontact marieflorescontact added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 5, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.10, Release 6.1.0 Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants