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]Incorrect sorting type for timestamp,Risk Score under Cases new alert tab #135101

Closed
ghost opened this issue Jun 24, 2022 · 6 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Cases Cases feature Feature:Detection Alerts Security Solution Detection Alerts Feature impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed

Comments

@ghost
Copy link

ghost commented Jun 24, 2022

Describe the bug
Incorrect sorting type for timestamp,Risk Score under Cases new alert tab

Build Details:

Version:8.3.0 BC8
Commit:a20413e97c4b30f3fae464b0992952a5fcba0445
Build:53497

preconditions

  • At least one alert attachment to case

Steps

  • Login to kibana and go to Security App
  • Go to Cases area and then new Alert tab
  • Check the sorting data type for timestamp is showing A-Z Z-A however it should be Old-New New-Old
  • Check the sorting data type for Risk Score is showing A-Z Z-A however it should be low-high high-low

Note:

  • Sorting is working correctly just UI issue

Screen-Shoot

image

image

@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Jun 24, 2022
@elasticmachine
Copy link
Contributor

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

@ghost ghost added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Jun 24, 2022
@ghost ghost assigned cnasikas Jun 24, 2022
@cnasikas
Copy link
Member

@XavierM Is this something we control or it is provided by the solutions?

@XavierM
Copy link
Contributor

XavierM commented Jun 24, 2022

I put it in our project board

@MindyRS MindyRS added the Feature:Detection Alerts Security Solution Detection Alerts Feature label Jun 29, 2022
@MadameSheema MadameSheema added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Jun 30, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@MadameSheema MadameSheema added the Feature:Cases Cases feature label Jun 30, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@jcger
Copy link
Contributor

jcger commented Sep 21, 2022

Fixed after closing #137988

@jcger jcger closed this as completed Sep 21, 2022
Repository owner moved this from In Review to Done in AppEx: ResponseOps - Rules & Alerts Management Sep 21, 2022
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 Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Cases Cases feature Feature:Detection Alerts Security Solution Detection Alerts Feature impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed
Projects
No open projects
Development

No branches or pull requests

6 participants