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] Sorting Not Working Alphabetically in Alerts Table #201467

Open
pborgonovi opened this issue Nov 22, 2024 · 4 comments
Open
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:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@pborgonovi
Copy link
Contributor

Describe the bug:

In the Alerts table, sorting alphabetically by specific columns (e.g., Rule Name, Severity) does not work as expected. However, sorting by Timestamp operates correctly. When attempting to sort alphabetically, the table rows do not reorder in either ascending or descending

Kibana/Elasticsearch Stack version:

8.17

Server OS version:

Browser and Browser OS versions:

Elastic Endpoint version:

Original install method (e.g. download page, yum, from source, etc.):

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

Pre requisites:

  1. Rules should be installed
  2. Alerts should have been generated

Steps to reproduce:

  1. Navigate to the Alerts table in the application.
  2. Select a column header with alphabetical data (e.g., Severity, or Rule name) to apply sorting.
  3. Observe the table contents.

Current behavior:

The table remains unchanged, and the sorting functionality does not reorder the rows.

Expected behavior:

The table should reorder its rows based on the selected column in the specified sorting order (ascending or descending).

Screenshots (if relevant):

Screen.Recording.2024-11-22.at.11.39.16.AM.mov
Screen.Recording.2024-11-22.at.11.46.39.AM.mov

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context (logs, chat logs, magical formulas, etc.):

@pborgonovi pborgonovi 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. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team triage_needed labels Nov 22, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@yctercero
Copy link
Contributor

@asnehalb @michaelolo24 I think this is threat hunting territory?

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:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

4 participants