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

SCA result filters do not work #4952

Closed
Rebits opened this issue Dec 2, 2022 · 2 comments · Fixed by #4999, #5004 or #5005
Closed

SCA result filters do not work #4952

Rebits opened this issue Dec 2, 2022 · 2 comments · Fixed by #4999, #5004 or #5005
Assignees
Labels
qa/report QA Team: Reporting possible bug type/bug Bug issue

Comments

@Rebits
Copy link
Member

Rebits commented Dec 2, 2022

Wazuh Elastic Rev Security
4.4 7.17 1
Browser
Chrome, Firefox, Safari, etc

Description
CIS benchmark status filters do not work properly

Preconditions

  1. Have a registered agent
  2. Have a finished SCA scan of the agent

Steps to reproduce

  1. Navigate to Modules>Agent name>Security configuration assessment
  2. Click on one of the filter buttons (Pass, Fail, or Not applicable)
  3. Check that no filter is applied.

Video

sca.webm
@Rebits Rebits added type/bug Bug issue qa/report QA Team: Reporting possible bug release test/4.4.0 labels Dec 2, 2022
@Rebits Rebits moved this to Triage in Release 4.4.0 Dec 2, 2022
@Tostti Tostti self-assigned this Dec 7, 2022
@davidjiglesias davidjiglesias moved this from Triage to In Progress in Release 4.4.0 Dec 13, 2022
@Machi3mfl Machi3mfl self-assigned this Dec 14, 2022
@Machi3mfl
Copy link
Member

Machi3mfl commented Dec 14, 2022

Replicated issue on Kibana v7.10.2

  • CIS benchmark status filters do not work properly when the user clicks the stats (Pass, Failed, Not Applicable)

Correct behavior

When the user clicks the stats the checks table should be filtered by the selected stat

@Desvelao
Copy link
Member

Changes

Fixed

  • Fixed the results stat buttons did not apply the filters to the search bar.

Changed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment